otherwise you’d be looking at very unwriter txs designed to create waste for the miners and stats OR a lot of people + a lot of cocaine + a twetch clone
Post by twetch#11711
CCC has two storage units of hard drives and documents being migrated to BSH, but that still wouldn’t take up 70% of BSV.
What the chain says
- Block
- 663 838
- Time
- 2020-12-02T16:36:48Z
- Signer
- 18ZWnrQ2ijRHUCKfWMot5iPCEGp4mWe2gL
- App
- twetch
- Type
- post
- Content type
- text/plain
- Name in tx
- twetch#11711
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
18ZWnrQ2ijRHUCKfWMot5iPCEGp4mWe2gL VerifiedReplies (8)
you can figure this one out w/ a desktop and an afternoon of cryptanalysis... just track the % and relative tx sizes before and after twetch was created
wouldn’t a metanet just be a surveillance network that annotates all the other transactions on chain (at least w/ an init tx followed by categorization txs) : @1 + @5
identifying an automation would be as simple as taking tx constants re: string length of various identifiers and dividing them over the metanet txs sizes
@2 : if $I was CSW $I would prune twetch txs after replaying them in a sub system that gives CSW royalties later when others can’t sync Twetch on chain w/o paying additional tolls
would also include GBs worth of noise every time $I mine a block to clog bandwidth and drives of nodes who try to sync w/o pruning