Author Topic: The "memo" field  (Read 2884 times)

0 Members and 1 Guest are viewing this topic.

Offline kenCode

storing a file on the chain is expensive ... storing a hash is not

ok cool, so it is possible then to store a file, that's great news!
1. how expensive and 2. how do we upload the mp3 file?
3. how do we store just the hash?
kenCode@Agorise
Matrix/Keybase/Blurt/Hive: @Agorise
Session: 0525c95e7f37dca6e29ac84fe7030f0bc5f8bcd564207f03c893e47d2a381a2337

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I think the only limiting factor is either the max tx size or the max block size ..

Note that for transfers you need to pay a "per kilo byte" fee .. hence storing a file on the chain is expensive ... storing a hash is not

Offline kenCode

1. How large is, or can the memo field be?
2. Does it now, or can it (in the near future) support HTML or BBCode for markup?
3a. Would it be possible to also add a BLOB (or similar) field for storing say, mp3 or mp4 6GB+ file(s) with that "memo" textarea?
 3b. or would Storj/Factom technology be needed for this feature?
kenCode@Agorise
Matrix/Keybase/Blurt/Hive: @Agorise
Session: 0525c95e7f37dca6e29ac84fe7030f0bc5f8bcd564207f03c893e47d2a381a2337