shibpost

{"p": "drc-20","op":"deploy", "tick": "lol", "m": "10100000", "l": "101"}

Israel bombs Syria

Elon announces creation of 'America Party'

FBI, DOJ say Epstein killed himself and there is no client list

Happy birthday, Elon!

Minor response to US bombing, US/Israel & Iran agree to Ceasefire

US bombs Iran

Defund Planned Parenthood! Prosecute Planned Parenthood!

Israel launches attack on Iran, missiles exchanged.

Trump/Elon feud cools off. Wishing each other well, Elon deletes Epstein posts.

Elon claims Trump appears in the Epstein files, real reason for non-release.

Elon & Trump publicly feud over deficit spending in Trump's 'Big Beautiful Bill'

I believe that the War in Ukraine is God's punishment (or karma) for abortions.

#doginals and #dunes #drc20 $dogi on dogecoin I like it all

Update: https://github.com/dogecoin/dogecoin/pull/3836

Pull Request, 80->420 bytes https://github.com/dogecoin/dogecoin/pull/3830

Removing OP_RETURN limits: https://github.com/dogecoin/dogecoin/discussions/3829

if the 80 byte limit is removed, then json in a single op_return with burn

not certain but i think its just a network relay rule

Is adding multi opreturns hardfork? I think maybe old nodes reject.

https://github.com/bitcoin/bitcoin/pull/32359 potentially removing 80b limit too

could set RefTxId OP_RETURN to 0 Doge, simpler and reduces cost even more.

Reftxid in opreturn_0 w reply in opreturn_1 better but doge wont likely change

need to future proof shibapost v2: https://github.com/bitcoin/bitcoin/pull/3238

posted wrong link lol: https://github.com/bitcoin/bitcoin/pull/32381

Fight for the truth! Putin is a dictator, Zelenskyj is NOT!

HAPPY EASTER DOGECOIN!!!!🥚🐰✝️

Supposedly some L2s are going to be launching for dogecoin soon...

right so op goes hash160(push32 [txid] drop true) to make addr redeemscript

Elon Musk, keep fighting corruption, keep fighting fraud, keep fighting lies!

so... "ShibaPost: Reply-V2 (p2sh): OP_PUSH32 [refTxId] OP_DROP OP_TRUE"?

Or rather: OP_PUSH32 [refTxidHash] OP_DROP OP_TRUE

Was thinking: OP_PUSH32 <TXID> OP_DROP OP_TRUE

or rather "ShibaPostV2: Reply (p2sh): OP_HASH256 [refTxIdHash] OP_EQUAL"?

eg 9tbvanok1FxmCTNUUm6t4ZLhKbXrrLuWoX as reply addr to OP txid 141f35..5688

you ok with "ShibaPostV2: Reply (p2sh): OP_HASH256 [refTxId] OP_EQUAL"?

OP_HASH256 <txid_hash> OP_EQUAL

apparently the &gtl; sign and &lt; sign are bugged on post creation...

freakin shibpost.com bugs lol.. best find them now OP_HASH256 TxIdHash OP_EQUAL

i like that a lot. OP_HASH256 <txid_hash> OP_EQUAL

Reply addr maybe p2sh w txid as hashpuzzle. Anyone can spend, but prevents bloat

also, shibpost.com is kinda buggy, but after 10 confirms should show correctly

right now, doge spent on reply addr isn't part of vote count so that makes sense

Love the protocol. Wonder if v2 might set reply address to spendable? Prevent ut

welcome! ❤️

Hello ShibePost! Hello world! Love, opreturn.net

you can 'fake' a high tx fee by mining an unbroadcasted tx in a block yourself

Elon Musk, please support pro-life in Europe too!

🔥🐶🪙 8urn Ð0g3c01n 0n 0p_r3turn utx0z 🔥🐶🪙

China imposes 125% tariff on US imports.