Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: transaction ids  (Read 334 times)

0 Members and 1 Guest are viewing this topic.

Offline monsterer

transaction ids
« on: November 23, 2014, 01:49:09 PM »

wallet_account_transaction_history lists what appear to be partial or truncated transaction ids. For example, I have d4d012f9 listed from that command. However, this doesn't appear to be enough to, for example, look up this transaction on bitsharesblocks.com.

Calling blockchain_get_transaction d4d012f9, I get a json dump of that transaction, where I can see it was in block 726271. blockchain_get_block 726271, shows me that my transaction was the only one in the block, and the full TXID is d4d012f9a517a5f7b1bdf0a8eeb39a3c24865df6 which starts with the partial id returned from wallet_account_transaction_history .

My question: how can I get this full TXID, or a list of full TXIDs from my wallet?
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12058
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Re: transaction ids
« Reply #1 on: November 23, 2014, 03:58:32 PM »
my guess whould be that the RPC call returns the FULL TXID and only the CLI truncates it  </wildguess>
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline monsterer

Re: transaction ids
« Reply #2 on: November 23, 2014, 05:54:36 PM »
my guess whould be that the RPC call returns the FULL TXID and only the CLI truncates it  </wildguess>

Hmm, I have often wondered why the command line gives you a different version of the RPC output from what you get in practice. Where's the best place to request they unify that?
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline pc

  • Hero Member
  • *****
  • Posts: 1012
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BTS: cyrano
  • Witness: cyrano
  • Payrate: 100%
Re: transaction ids
« Reply #3 on: November 23, 2014, 07:47:31 PM »
Obviously the command line is meant for interactive use. It makes sense to display things in a simplified way that's easier to parse by the human eye.

RPC is meant to be used programmatically. Here, structure is more important than simplicity.

IOW it makes sense the way it is. If you still want to have this unified, I suggest you open a feature request on github.
Please vote for my BitShares witness "cyrano" and for my STEEM witness "cyrano.witness"!
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline vikram

Re: transaction ids
« Reply #4 on: November 23, 2014, 08:10:57 PM »
Using the command line interface, many of the commands are pretty-printed for interactive use as pc said. You can see the raw output by using the "enable_raw" command first.

I've made a note about getting the full txid: https://github.com/BitShares/bitshares/issues/1048

Offline monsterer

Re: transaction ids
« Reply #5 on: November 23, 2014, 10:02:46 PM »
Using the command line interface, many of the commands are pretty-printed for interactive use as pc said. You can see the raw output by using the "enable_raw" command first.

I've made a note about getting the full txid: https://github.com/BitShares/bitshares/issues/1048

enable_raw, perfect. And thanks for creating the feature request!
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

 

Google+