Peck by utxo detective

1harry…c9EQ Key · twetch

if we want to post over 100kb we need to start broadcasting over 100kb, if we want lower sats/byte we need to boradcast lower sats/byte. We must push limits to find the boundaries

What the chain says

Transaction: 837ed7d2b2b98c78b4a35292c5a6e1cb9e01f7a92d2c66b1278f41e95037f4cd
Block: 620 633
Time: 2020-02-04T20:01:26Z
Signer: 1harrywon46Aq2b2TK29wKviKUiDzc9EQ
App: twetch
Type: post
Content type: text/plain

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 1harrywon46Aq2b2TK29wKviKUiDzc9EQ Verified

Replies (4)

twetch#622 6.7y

1JLBut…aTuZ Key · twetch

Replying to@1harry…c9EQ

Absolutely. Create the demand pressure to tempt miners into expanding their limits.

twetch#2159 6.7y

1JLBut…aTuZ Key · twetch

Replying to@1harry…c9EQ

Just thinking 🤔... a simple way to push the boundaries might be to make it possible for users to create a Twetch with x replies under it. 1 reason being sometimes you are writing one and don’t know how many it will take and people comment or branch early

twetch#2159 6.7y

1JLBut…aTuZ Key · twetch

Replying to@1JLBut…aTuZ

I think limiting the text size is actually important because everyone is on smartphones and huge Twetches would ruin the experience but a Twetch with replies is good as the main Twetch should draw someone in to read replies.

twetch#2159 6.7y

1JLBut…aTuZ Key · twetch

Replying to@1JLBut…aTuZ

I should add I mean if it was possible to batch a Twetch with replies together into 1 transaction.

Post by utxo detective

Replies (4)