Author Topic: Increase the memo field in the transaction to 64 characters  (Read 6523 times)

0 Members and 1 Guest are viewing this topic.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
It was either 19 or 35 due to aes encryption chunk size.
so what's the argument against increasing the memo size to 35 bytes again?

Offline bytemaster

It was either 19 or 35 due to aes encryption chunk size. 
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline svk

according to
https://github.com/BitShares/bitshares/blob/master/libraries/blockchain/include/bts/blockchain/config.hpp#L39

The memo limit is currently 19bytes .. for a ripemd160 hash of a public key you need 160bit which is 20 byte ..
so actually we are very close to what is required .. increasing the limit to 20bytes would be enough ..

not sure what the argumentation has been to set it at 19bytes in the first place
I think they lowered it for v0.4.27 actually, I know at one point I could no longer use the same memo I had used before.  It even caused those transactions that had the earlier, longer memos to disappear from my transaction history.
Worker: dev.bitsharesblocks

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
according to
https://github.com/BitShares/bitshares/blob/master/libraries/blockchain/include/bts/blockchain/config.hpp#L39

The memo limit is currently 19bytes .. for a ripemd160 hash of a public key you need 160bit which is 20 byte ..
so actually we are very close to what is required .. increasing the limit to 20bytes would be enough ..

not sure what the argumentation has been to set it at 19bytes in the first place

Offline cass

  • Hero Member
  • *****
  • Posts: 4311
  • /(┬.┬)\
    • View Profile
█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█

Offline monsterer

Good idea.
Maybe charge an extra high transaction fee for long memos to avoid bloat?

Yeah, maybe transaction fee could be per kb?
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline Markus

  • Sr. Member
  • ****
  • Posts: 366
    • View Profile
Good idea.
Maybe charge an extra high transaction fee for long memos to avoid bloat?

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
That way a memo can reference a bitcoin address, or bitcoin TXID as well as bitshares trxid and account name.

The current length cant even accommodate a bitcoin address.
+5

Sent from my ALCATEL ONE TOUCH 997D


Offline monsterer

That way a memo can reference a bitcoin address, or bitcoin TXID as well as bitshares trxid and account name.

The current length cant even accommodate a bitcoin address.

use case: gateways - having the user put their desired bitcoin address into the memo field of a bitshares transaction removes the need to import private keys into the bitshares wallet, which is fragile and only works once due to change addresses.
« Last Edit: January 15, 2015, 09:25:49 am by monsterer »
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads