$RDT is now trading on Uniswap v2!
✅ Contract Address: 0xc03079Cf5732a9B06f0E41359fE6268b5AD55bF5
📈 Price Chart: https://t.co/BuRvsZE1f2
Don't miss out on this opportunity!
#RuneData
Check Your $RDT Token Airdrop Eligibility 🔍
➡️ $RB holders can check their wallet address here: https://t.co/U0c4dgOXDH
✅ The $RDT token is pre-sale here: https://t.co/YM047xVW9r
💎 The $RDT token will launch on Uniswap at 3pm UTC today. You can claim the airdrop in a few hours.
#RuneData - $RDT Pre-sale
⏳ Countdown: 23 hours left
👉Get ready to join the Launchpad on #RunesBridge: https://t.co/7Ir9PAAR6H
First Launchpad #Runes 🥇
#RUNESBRIDGE LAUNCHPAD - RUNEDATA ✅
➡️Official Link: https://t.co/YM047xVW9r
1/ Information
🔹Name: RuneData
🔹Social: @RuneData_io
🔹Symbols: $RDT
🔹Supply: 100,000,000 🌐
🔹Address on #Runes: https://t.co/x0ojLuqops
🔹Address on #Ethereum: 0x7a5C25216A674502e26bFA3E2f642f290b906e43
🔹Tokenomics: 55% Pre-sale, 35% Liquidity on Ethereum, 5% Airdrop $RB holders, 3% Rewards Platform, 2% Marketing (details: https://t.co/9Ml4rZ396V)
2/ Pre-sale
🔹Softcap: 50 ETH
🔹Hardcap: 125 ETH
🔹Ratio: 1 ETH = 440,000 RDT
🔹Max buy: 0.25 ETH - $RB stakers who accumulate over 20,000 points will be able to buy a maximum amount of ETH: points*0.25/20000
🔹Fund allocation: 63.64% Liquidity, 36.36% Infrastructure
🔹Start: 2pm UTC, Jun 17, 2024
🔹End: 2pm UTC, Jun 19, 2024 (or reached hardcap)
3/ Distribution
🔹Pre-sale: TGE 100% on #Runes - After the end of Presale 24 hours
🔹Airdrop: TGE 25% on #Runes - After the end of Presale 48 hours (Snapshot on Jun 17, 2024 - we will announce details soon)
ℹ️Note: The $RDT token is Pre-sale on the Ethereum chain and distributed on #Runes, so you need to provide a BTC wallet address when joining Launchpad.
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 😅
#RuneData - #Runes Explorer Is Live On Mainnet ✅
➡️Mainnet: https://t.co/IErM0ppQQC
➡️Testnet: https://t.co/epm9ATLFn4
🤝Powered by @RunicLayer2 & @RunesBridge
#RuneData - #Runes Explorer
✅ Updated to ord 0.18.1 (latest)
✅ Fix indexer blockage
✅ Add etching turbo flag
✅ Add sorting features
https://t.co/IErM0ppQQC
#RuneData Is Live On Testnet ✅
We are constantly updated with the latest changes from Casey and the developers on the #Runes protocol.
1/ Overview - Quickly track Runes statistics
👉https://t.co/IErM0ppQQC