Similar to "View Block" it would be ideal to also have "View transaction" so users can basically verify anything they see on an explorer with their local node. This code will need to be slightly different than "View Block" because different data is known about a tx depending on if we were the sender, receiver or not involved in it and also if it was a coinbase tx, t2z, t2t, or z2z.
Similar to "View Block" it would be ideal to also have "View transaction" so users can basically verify anything they see on an explorer with their local node. This code will need to be slightly different than "View Block" because different data is known about a tx depending on if we were the sender, receiver or not involved in it and also if it was a coinbase tx, t2z, t2t, or z2z.
Currently we only use getrawtransaction RPC but I tested z_viewtransaction and it did work. We now have a basic implementation of this on the dev branch. It needs some tweaks to render more of the data, for instance it doesn't render any of the data in the arrays of transparent inputs/outputs and shielded inputs/outputs. There is also a bug where valueBalance is being treated as a double instead of a string and it being incorrectly rounded.
Currently we only use `getrawtransaction` RPC but I tested `z_viewtransaction` and it did work. We now have a basic implementation of this on the `dev` branch. It needs some tweaks to render more of the data, for instance it doesn't render any of the data in the arrays of transparent inputs/outputs and shielded inputs/outputs. There is also a bug where `valueBalance` is being treated as a double instead of a string and it being incorrectly rounded.
The most intuitive UI for this is for a user to right click on a tx in their Transactions tab and choose "View Transaction". That needs to be added, which will require refactoring the code. Currently the code assumes a popup window is needed to ask for a txid, but the above UI already knows the txid and just renders the data
The most intuitive UI for this is for a user to right click on a tx in their Transactions tab and choose "View Transaction". That needs to be added, which will require refactoring the code. Currently the code assumes a popup window is needed to ask for a txid, but the above UI already knows the txid and just renders the data
Right click menu option was added. Also, current behavior is that double clicking on a tx in the tx tab allows a user to reply to a memo in that tx, if it exists, otherwise double clicking does nothing. Now, if there is no memo, double clicking on a tx will show the View Transaction popup.
Currently rendering transparent inputs and shielded outputs is implemented.
Right click menu option was added. Also, current behavior is that double clicking on a tx in the tx tab allows a user to reply to a memo in that tx, if it exists, otherwise double clicking does nothing. Now, if there is no memo, double clicking on a tx will show the View Transaction popup.
Currently rendering transparent inputs and shielded outputs is implemented.
Similar to "View Block" it would be ideal to also have "View transaction" so users can basically verify anything they see on an explorer with their local node. This code will need to be slightly different than "View Block" because different data is known about a tx depending on if we were the sender, receiver or not involved in it and also if it was a coinbase tx, t2z, t2t, or z2z.
The RPCs that we will need to talk to work on this include
getrawtransactionandz_viewtransactionwhich need to be added to SD.RPC method for
z_viewtransactionhas been added to the dev branchgetrawtransactionis on dev now as wellCurrently we only use
getrawtransactionRPC but I testedz_viewtransactionand it did work. We now have a basic implementation of this on thedevbranch. It needs some tweaks to render more of the data, for instance it doesn't render any of the data in the arrays of transparent inputs/outputs and shielded inputs/outputs. There is also a bug wherevalueBalanceis being treated as a double instead of a string and it being incorrectly rounded.The most intuitive UI for this is for a user to right click on a tx in their Transactions tab and choose "View Transaction". That needs to be added, which will require refactoring the code. Currently the code assumes a popup window is needed to ask for a txid, but the above UI already knows the txid and just renders the data
Right click menu option was added. Also, current behavior is that double clicking on a tx in the tx tab allows a user to reply to a memo in that tx, if it exists, otherwise double clicking does nothing. Now, if there is no memo, double clicking on a tx will show the View Transaction popup.
Currently rendering transparent inputs and shielded outputs is implemented.
Things that still need to be rendered: