Quote from: bytemaster on January 15, 2015, 01:15:29 PM
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?

It was either 19 or 35 due to aes encryption chunk size. 

Quote from: xeroc on January 15, 2015, 12:35:01 PM
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.

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

IMO good idea

Quote from: Markus on January 15, 2015, 10:04:13 AM
Good idea.
Maybe charge an extra high transaction fee for long memos to avoid bloat?

Yeah, maybe transaction fee could be per kb?

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

Quote from: monsterer on January 15, 2015, 09:07:15 AM
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

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.