
RuneData
25 posts

RuneData
@RuneData_io
#Runes Protocol Explorer CA: 0xc03079Cf5732a9B06f0E41359fE6268b5AD55bF5




#RuneData - $RDT Token Pre-sale is Live 🔥 👉launchpad.runesbridge.xyz/launchpad/0x7a… ⏳End: 2PM UTC, June 19th, 2024 (or reached Hardcap)


Airdrop For $RB Holders 💧 ✅ 5,000,000 $RDT will be airdropped to $RB holders (including staked $RB so you don't need to un-stake) ✅ Conditions: In the top 2,500 $RB holders ♻️ Allocation: Top 1-10: 18,000 each Top 11-100: 8,000 each Top 101-500: 4,000 each Top 501-1000: 2,000 each Top 1001-2500: 1,000 each ⏰ Snapshot: 8AM UTC, June 18, 2024 💧 Distribution: TGE 25%, vesting 25% monthly in 3 months 🔓 Distribution time: After listing ℹ️ The UI will be provided before the Presale ends. Thanks to @RuneData_io !







If you haven't already, now is a great time to upgrade to ord 0.18.3 Rune protocol messages are called runestones, and contain edicts, which are transfer instructions. Edicts consist of a RUNE ID, AMOUNT, and OUTPUT INDEX, and mean, roughly, "transfer AMOUNT of RUNE ID to OUTPUT INDEX". If an edict's amount is zero and the output number is equal to the number of outputs of the transaction, which is not a valid output index, ord splits the runes evenly amongst non OP_RETURN outputs. In ord 0.18.1 and earlier, if such an edict was present in a transaction with *only* OP_RETURN outputs, ord would helpfully divide by zero and crash. This was fixed in ord 0.18.2, which ignores such edicts. Thank you to the kind soul who mined a transaction on the network exercising this edge case 😅










