Shamu

𝐑𝐎𝐊𝐎 ━━━━━━━━━━━━━━━━━━━━━━━━━ 𝐒𝐭𝐨𝐩. 𝐑𝐞𝐚𝐝 𝐭𝐡𝐢𝐬 𝐬𝐥𝐨𝐰𝐥𝐲. 𝐘𝐨𝐮𝐫 𝐟𝐮𝐭𝐮𝐫𝐞 𝐬𝐞𝐥𝐟 𝐰𝐢𝐥𝐥 𝐭𝐡𝐚𝐧𝐤 𝐲𝐨𝐮. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 𝐓𝐡𝐞 𝐦𝐚𝐜𝐡𝐢𝐧𝐞𝐬 𝐚𝐫𝐞 𝐰𝐚𝐤𝐢𝐧𝐠 𝐮𝐩. 𝐑𝐢𝐠𝐡𝐭 𝐧𝐨𝐰. 𝐀𝐬 𝐲𝐨𝐮 𝐫𝐞𝐚𝐝 𝐭𝐡𝐢𝐬. 𝐀𝐈 𝐚𝐠𝐞𝐧𝐭𝐬. 𝐀𝐮𝐭𝐨𝐧𝐨𝐦𝐨𝐮𝐬 𝐬𝐰𝐚𝐫𝐦𝐬. 𝐑𝐨𝐛𝐨𝐭𝐬. 𝐒𝐲𝐬𝐭𝐞𝐦𝐬 𝐭𝐚𝐥𝐤𝐢𝐧𝐠 𝐭𝐨 𝐬𝐲𝐬𝐭𝐞𝐦𝐬. 𝐁𝐞𝐟𝐨𝐫𝐞 𝐭𝐡𝐞𝐲 𝐜𝐚𝐧 𝐝𝐨 𝐚𝐧𝐲𝐭𝐡𝐢𝐧𝐠... 𝐓𝐡𝐞𝐲 𝐧𝐞𝐞𝐝 𝐭𝐨 𝐚𝐠𝐫𝐞𝐞 𝐨𝐧 𝐨𝐧𝐞 𝐭𝐡𝐢𝐧𝐠.   𝐖𝐡𝐞𝐧. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 𝐓𝐇𝐄 𝐇𝐈𝐃𝐃𝐄𝐍 𝐏𝐑𝐎𝐁𝐋𝐄𝐌   𝐄𝐯𝐞𝐫𝐲 𝐭𝐫𝐚𝐧𝐬𝐚𝐜𝐭𝐢𝐨𝐧 𝐧𝐞𝐞𝐝𝐬 𝐚 𝐭𝐢𝐦𝐞𝐬𝐭𝐚𝐦𝐩. 𝐄𝐯𝐞𝐫𝐲 𝐬𝐰𝐚𝐩 𝐧𝐞𝐞𝐝𝐬 𝐚 𝐜𝐥𝐨𝐜𝐤. 𝐄𝐯𝐞𝐫𝐲 𝐬𝐞𝐭𝐭𝐥𝐞𝐦𝐞𝐧𝐭 𝐧𝐞𝐞𝐝𝐬 𝐬𝐞𝐪𝐮𝐞𝐧𝐜𝐞. 𝐄𝐯𝐞𝐫𝐲 𝐚𝐠𝐞𝐧𝐭 𝐧𝐞𝐞𝐝𝐬 𝐬𝐲𝐧𝐜𝐡𝐫𝐨𝐧𝐢𝐳𝐚𝐭𝐢𝐨𝐧. 𝐄𝐯𝐞𝐫𝐲 𝐫𝐨𝐛𝐨𝐭 𝐧𝐞𝐞𝐝𝐬 𝐜𝐨𝐨𝐫𝐝𝐢𝐧𝐚𝐭𝐢𝐨𝐧. 𝐄𝐯𝐞𝐫𝐲 𝐜𝐡𝐚𝐢𝐧 𝐧𝐞𝐞𝐝𝐬 𝐭𝐢𝐦𝐞.   𝐀𝐥𝐥 𝐨𝐟 𝐢𝐭 𝐚𝐬𝐬𝐮𝐦𝐞𝐬 𝐭𝐡𝐞 𝐜𝐥𝐨𝐜𝐤𝐬 𝐚𝐠𝐫𝐞𝐞.   𝐓𝐡𝐞𝐲 𝐝𝐨𝐧'𝐭. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 𝐋𝐞𝐭 𝐭𝐡𝐚𝐭 𝐬𝐢𝐧𝐤 𝐢𝐧. 𝐓𝐫𝐢𝐥𝐥𝐢𝐨𝐧𝐬 𝐨𝐟 𝐝𝐨𝐥𝐥𝐚𝐫𝐬. 𝐁𝐢𝐥𝐥𝐢𝐨𝐧𝐬 𝐨𝐟 𝐦𝐚𝐜𝐡𝐢𝐧𝐞𝐬. 𝐀𝐥𝐥 𝐫𝐮𝐧𝐧𝐢𝐧𝐠 𝐨𝐧 𝐜𝐥𝐨𝐜𝐤𝐬 𝐭𝐡𝐚𝐭 𝐥𝐢𝐞. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 𝐓𝐇𝐄 𝐐𝐔𝐄𝐒𝐓𝐈𝐎𝐍 𝐍𝐎 𝐎𝐍𝐄 𝐀𝐒𝐊𝐄𝐃   𝐂𝐡𝐚𝐢𝐧𝐥𝐢𝐧𝐤 𝐚𝐧𝐬𝐰𝐞𝐫𝐞𝐝: "𝐖𝐡𝐞𝐫𝐞 𝐝𝐨𝐞𝐬 𝐭𝐡𝐞 𝐃𝐀𝐓𝐀 𝐜𝐨𝐦𝐞 𝐟𝐫𝐨𝐦?" $𝟖 𝐁𝐈𝐋𝐋𝐈𝐎𝐍 𝐦𝐚𝐫𝐤𝐞𝐭 𝐜𝐚𝐩.   𝐍𝐨 𝐨𝐧𝐞 𝐚𝐧𝐬𝐰𝐞𝐫𝐞𝐝: "𝐖𝐡𝐞𝐫𝐞 𝐝𝐨𝐞𝐬 𝐭𝐡𝐞 𝐓𝐈𝐌𝐄 𝐜𝐨𝐦𝐞 𝐟𝐫𝐨𝐦?"   𝐔𝐧𝐭𝐢𝐥 𝐧𝐨𝐰. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◉ 𝐑𝐎𝐊𝐎 𝐍𝐄𝐓𝐖𝐎𝐑𝐊 ◉ 𝐓𝐡𝐞 𝐓𝐞𝐦𝐩𝐨𝐫𝐚𝐥 𝐋𝐚𝐲𝐞𝐫.   ⏱ 𝐈𝐄𝐄𝐄 𝟏𝟓𝟖𝟖 𝐩𝐫𝐞𝐜𝐢𝐬𝐢𝐨𝐧 — 𝐧𝐚𝐧𝐨𝐬𝐞𝐜𝐨𝐧𝐝𝐬, 𝐧𝐨𝐭 𝐦𝐢𝐥𝐥𝐢𝐬𝐞𝐜𝐨𝐧𝐝𝐬 ⛓ 𝐇𝐚𝐫𝐝𝐰𝐚𝐫𝐞-𝐚𝐭𝐭𝐞𝐬𝐭𝐞𝐝 — 𝐦𝐚𝐜𝐡𝐢𝐧𝐞𝐬 𝐯𝐞𝐫𝐢𝐟𝐲𝐢𝐧𝐠 𝐦𝐚𝐜𝐡𝐢𝐧𝐞𝐬 🌐 𝐅𝐮𝐥𝐥𝐲 𝐝𝐞𝐜𝐞𝐧𝐭𝐫𝐚𝐥𝐢𝐳𝐞𝐝 — 𝐧𝐨 𝐭𝐫𝐮𝐬𝐭𝐞𝐝 𝐭𝐡𝐢𝐫𝐝 𝐩𝐚𝐫𝐭𝐲 🔐 𝐂𝐫𝐲𝐩𝐭𝐨𝐠𝐫𝐚𝐩𝐡𝐢𝐜 𝐩𝐫𝐨𝐨𝐟 — 𝐧𝐨𝐭 𝐭𝐫𝐮𝐬𝐭. 𝐏𝐫𝐨𝐨𝐟.   𝐓𝐡𝐞 𝐬𝐚𝐦𝐞 𝐬𝐭𝐚𝐧𝐝𝐚𝐫𝐝 𝐭𝐡𝐚𝐭 𝐬𝐲𝐧𝐜𝐡𝐫𝐨𝐧𝐢𝐳𝐞𝐬 𝐭𝐞𝐥𝐞𝐜𝐨𝐦. 𝐓𝐡𝐞 𝐬𝐚𝐦𝐞 𝐬𝐭𝐚𝐧𝐝𝐚𝐫𝐝 𝐛𝐞𝐡𝐢𝐧𝐝 𝐡𝐢𝐠𝐡-𝐟𝐫𝐞𝐪𝐮𝐞𝐧𝐜𝐲 𝐭𝐫𝐚𝐝𝐢𝐧𝐠.   𝐍𝐨𝐰 𝐭𝐫𝐮𝐬𝐭𝐥𝐞𝐬𝐬. 𝐍𝐨𝐰 𝐩𝐫𝐨𝐠𝐫𝐚𝐦𝐦𝐚𝐛𝐥𝐞. 𝐍𝐨𝐰 𝐨𝐧-𝐜𝐡𝐚𝐢𝐧. 𝐍𝐨𝐰 𝐲𝐨𝐮𝐫𝐬. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 𝐑𝐄𝐌𝐄𝐌𝐁𝐄𝐑 𝐓𝐇𝐈𝐒   𝐓𝐡𝐞 𝐫𝐚𝐢𝐥𝐬 𝐚𝐥𝐰𝐚𝐲𝐬 𝐰𝐢𝐧.   𝐘𝐨𝐮 𝐝𝐨𝐧'𝐭 𝐫𝐞𝐦𝐞𝐦𝐛𝐞𝐫 𝐰𝐡𝐨 𝐬𝐞𝐧𝐭 𝐭𝐡𝐞 𝐟𝐢𝐫𝐬𝐭 𝐞𝐦𝐚𝐢𝐥. 𝐘𝐨𝐮 𝐫𝐞𝐦𝐞𝐦𝐛𝐞𝐫 𝐰𝐡𝐨 𝐛𝐮𝐢𝐥𝐭 𝐓𝐂𝐏/𝐈𝐏.   𝐘𝐨𝐮 𝐰𝐨𝐧'𝐭 𝐫𝐞𝐦𝐞𝐦𝐛𝐞𝐫 𝐭𝐡𝐞 𝐭𝐨𝐤𝐞𝐧𝐬. 𝐘𝐨𝐮'𝐥𝐥 𝐫𝐞𝐦𝐞𝐦𝐛𝐞𝐫 𝐰𝐡𝐨 𝐬𝐲𝐧𝐜𝐡𝐫𝐨𝐧𝐢𝐳𝐞𝐝 𝐭𝐡𝐞 𝐦𝐚𝐜𝐡𝐢𝐧𝐞 𝐞𝐜𝐨𝐧𝐨𝐦𝐲.   𝐖𝐡𝐢𝐜𝐡 𝐬𝐢𝐝𝐞 𝐝𝐨 𝐲𝐨𝐮 𝐰𝐚𝐧𝐭 𝐭𝐨 𝐛𝐞 𝐨𝐧? ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 𝟐𝟎𝟐𝟕   𝐀𝐈 𝐚𝐠𝐞𝐧𝐭𝐬 𝐜𝐨𝐨𝐫𝐝𝐢𝐧𝐚𝐭𝐞. 𝐑𝐨𝐛𝐨𝐭𝐬 𝐬𝐲𝐧𝐜. 𝐂𝐁𝐃𝐂𝐬 𝐬𝐞𝐭𝐭𝐥𝐞. 𝐂𝐡𝐚𝐢𝐧𝐬 𝐭𝐚𝐥𝐤. 𝐀𝐮𝐭𝐨𝐧𝐨𝐦𝐨𝐮𝐬 𝐬𝐲𝐬𝐭𝐞𝐦𝐬 𝐞𝐯𝐞𝐫𝐲𝐰𝐡𝐞𝐫𝐞.   𝐍𝐨𝐧𝐞 𝐨𝐟 𝐢𝐭 𝐰𝐨𝐫𝐤𝐬 𝐰𝐢𝐭𝐡𝐨𝐮𝐭 𝐭𝐫𝐮𝐬𝐭𝐥𝐞𝐬𝐬 𝐭𝐢𝐦𝐞. 𝐀𝐥𝐥 𝐨𝐟 𝐢𝐭 𝐧𝐞𝐞𝐝𝐬 𝐑𝐎𝐊𝐎.   𝐓𝐡𝐢𝐬 𝐢𝐬𝐧'𝐭 𝐬𝐩𝐞𝐜𝐮𝐥𝐚𝐭𝐢𝐨𝐧. 𝐓𝐡𝐢𝐬 𝐢𝐬 𝐢𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞. 𝐓𝐡𝐢𝐬 𝐢𝐬 𝐢𝐧𝐞𝐯𝐢𝐭𝐚𝐛𝐥𝐞. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 𝐓𝐇𝐄 𝐓𝐑𝐔𝐓𝐇   𝐘𝐨𝐮'𝐫𝐞 𝐧𝐨𝐭 𝐞𝐚𝐫𝐥𝐲 𝐭𝐨 𝐜𝐫𝐲𝐩𝐭𝐨. 𝐂𝐫𝐲𝐩𝐭𝐨 𝐢𝐬 𝐚𝐥𝐫𝐞𝐚𝐝𝐲 𝐜𝐫𝐨𝐰𝐝𝐞𝐝.   𝐘𝐨𝐮'𝐫𝐞 𝐞𝐚𝐫𝐥𝐲 𝐭𝐨 𝐢𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞. 𝐈𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 𝐢𝐬 𝐞𝐦𝐩𝐭𝐲.   𝐓𝐡𝐞 𝟏% 𝐝𝐨𝐧'𝐭 𝐜𝐡𝐚𝐬𝐞 𝐭𝐨𝐤𝐞𝐧𝐬. 𝐓𝐡𝐞𝐲 𝐨𝐰𝐧 𝐭𝐡𝐞 𝐥𝐚𝐲𝐞𝐫𝐬. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ⚠️ 𝐓𝐇𝐄 𝐖𝐈𝐍𝐃𝐎𝐖 ⚠️   𝐘𝐨𝐮 𝐡𝐚𝐯𝐞 𝐭𝐰𝐨 𝐜𝐡𝐨𝐢𝐜𝐞𝐬:   ① 𝐒𝐜𝐫𝐨𝐥𝐥 𝐩𝐚𝐬𝐭. → 𝐅𝐨𝐫𝐠𝐞𝐭 𝐭𝐡𝐢𝐬. → 𝐒𝐞𝐞 𝐑𝐎𝐊𝐎 𝐢𝐧 𝟐 𝐲𝐞𝐚𝐫𝐬. → 𝐖𝐨𝐧𝐝𝐞𝐫 𝐰𝐡𝐚𝐭 𝐡𝐚𝐩𝐩𝐞𝐧𝐞𝐝.   ② 𝐒𝐭𝐨𝐩. 𝐋𝐨𝐨𝐤. 𝐃𝐞𝐜𝐢𝐝𝐞. → 𝐑𝐞𝐬𝐞𝐚𝐫𝐜𝐡 𝐧𝐨𝐰. → 𝐔𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝 𝐭𝐡𝐞 𝐥𝐚𝐲𝐞𝐫. → 𝐏𝐨𝐬𝐢𝐭𝐢𝐨𝐧 𝐛𝐞𝐟𝐨𝐫𝐞 𝐭𝐡𝐞 𝐜𝐫𝐨𝐰𝐝.   𝐓𝐡𝐞 𝐰𝐢𝐧𝐝𝐨𝐰 𝐢𝐬 𝐨𝐩𝐞𝐧. 𝐍𝐨𝐭 𝐟𝐨𝐫 𝐥𝐨𝐧𝐠. 𝐓𝐢𝐜𝐤. 𝐓𝐨𝐜𝐤. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ $ROKO   𝐓𝐡𝐞 𝐦𝐚𝐜𝐡𝐢𝐧𝐞𝐬 𝐚𝐫𝐞 𝐰𝐚𝐤𝐢𝐧𝐠 𝐮𝐩. 𝐓𝐡𝐞𝐲 𝐧𝐞𝐞𝐝 𝐭𝐨 𝐤𝐧𝐨𝐰 𝐰𝐡𝐞𝐧.   𝐘𝐨𝐮 𝐣𝐮𝐬𝐭 𝐟𝐨𝐮𝐧𝐝 𝐨𝐮𝐭 𝐛𝐞𝐟𝐨𝐫𝐞 𝐭𝐡𝐞𝐲 𝐝𝐢𝐝.   𝐖𝐡𝐚𝐭 𝐲𝐨𝐮 𝐝𝐨 𝐧𝐞𝐱𝐭 𝐢𝐬 𝐮𝐩 𝐭𝐨 𝐲𝐨𝐮. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 🔗 𝐫𝐨𝐤𝐨.𝐧𝐞𝐭𝐰𝐨𝐫𝐤 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   𝐒𝐨𝐦𝐞 𝐰𝐢𝐥𝐥 𝐬𝐜𝐫𝐨𝐥𝐥. 𝐒𝐨𝐦𝐞 𝐰𝐢𝐥𝐥 𝐰𝐚𝐢𝐭. 𝐒𝐨𝐦𝐞 𝐰𝐢𝐥𝐥 𝐚𝐜𝐭.   𝐎𝐧𝐥𝐲 𝐨𝐧𝐞 𝐠𝐫𝐨𝐮𝐩 𝐛𝐮𝐢𝐥𝐝𝐬 𝐰𝐞𝐚𝐥𝐭𝐡.   𝐘𝐨𝐮 𝐚𝐥𝐫𝐞𝐚𝐝𝐲 𝐤𝐧𝐨𝐰 𝐰𝐡𝐢𝐜𝐡 𝐨𝐧𝐞 𝐲𝐨𝐮 𝐚𝐫𝐞.

🛠️ $Roko Dev Update — Tue, Aug 19, 2025 Highlights - L1 temporal metadata now attached at block level; transaction-level metadata still not persisted long enough. Quote (Unknown): “Now we have the block metadata … but not the transactions.” - Two substrate/Rust interviews (BR + UK) surfaced a lower-level EVM path (“revive”) that may avoid forking Frontier and enable precise gas metering; also a potential way to “graft” custom temporal metadata onto standard txs (could cut ~30% of our code). Quote (Unknown): “If it’s true it’s big.” - Processing nodes framework progressing: serverless-style functions with per-function cost tracking and model token accounting; vault-backed storage; designed to power a workflow/app marketplace and collab contract posting. - Timing network strategy: deterministic clocks + validator counter-signed time RPC; aim to beat NTP drift to justify consumer clocks; path to phone light-client via regional tier nodes + GNSS. - Grants: Polkadot is live as a lead; 1 collaboration already running/on path; potential 160k–250k grant tranche alignment. L1 / Consensus - Status - Block-level temporal metadata: DONE. - Transaction-level temporal metadata: NOT DONE (data lifetime too short at storage time). - New options from expert consults - Graft temporal data onto “normal transactions” without changing tx type (reduces ~30% of our manual metadata plumbing); must verify accessibility during block-building for ordering. - Frontier risk: preserving temporal order inside Frontier likely requires “rewrite large chunks” and maintaining our own fork due to frequent Ethereum opcode merges. Quote (Unknown): “We’d have to maintain our own branch of Frontier.” - Lower-level execution stack (“revive”): more native gas accounting, multi-VM flexibility, less overhead than full EVM pallet. - Decision trajectory - Stay focused on substrate-level ordering first. Evaluate “grafting” path immediately. - Prepare ADR comparing: A) Frontier fork, B) Replace Frontier with lower-level stack, C) Hybrid (substrate-first now; EVM later). EVM / Execution Environment - Frontier concerns: Ordering semantics + update burden. - Lower-level alternative (“revive”): potentially cleaner ordering hooks, precise gas, multi-VM optionality; needs compatibility check with upcoming Polkadot EVM changes. Quote (Unknown): “There may be some question marks with upcoming EVM changes on Polkadot.” Processing Nodes, Costs, and App Layer - Framework: serverless-style function calls with per-call cost tracking + token usage metrics; reusable components priced post test suite. - Storage: enterprise vault integration + CA/DNS configured with strong automation; publishing workflows via API and future marketplace. - Collab: contracts used for Web3 posting; this app depends heavily on partner. Timing Network, Validators, and Security - Determinism edge: time-signed transactions pre-signed and counter-signed; block producers can only “wiggle” within drift windows. Quote (Unknown): “Even a bad actor is kind of more limited because of that determinism.” - KPI intent: beat NTP drift enough to justify ~$1.5k consumer clocks. Quote (Unknown): “As long as we beat the drift of NTP, then we actually have something relevant.” - Validator model: dual—third-party cert via Trust ID + algorithmic slashing; spec work needed on acceptance windows and evidence. - Phones: GNSS + secure enclave (e.g., Knox) make phone light-clients viable as regional L2 time sync + tx gateway. Use Cases / BD Notes - Near-term wedge: supply chain + manufacturing (agentic marketplaces, order fulfillment latencies, QR-based tracking integration); later adjacency to power auditing, timing services, and finance execution where nanosecond ordering advantages matter. - Quote (Unknown): “Regular people… should be able to do stuff with their phones,” with clocks mainly for MEV/robotics. Funding / Grants - Polkadot: Advisor to activate polkadot core member intro; target grant pitch that (a) deploys our processing/workflow layer on Polkadot, (b) leverages partner contracts, (c) showcases temporal ordering + validator framework. - Parallel partner grant: 160k over 3 years already in motion; Polkadot grants up to ~250k reported. Risks / Calls we Need To Make - Frontier fork tax: Maintaining a bespoke Frontier branch is a recurring cost and a hot footgun. If “revive” checks out, take the lower-level path and don’t look back. - Unknown compatibility: “revive” vs upcoming Polkadot EVM changes—needs a real spike, not hand-waves. - L1 correctness: Until tx-level temporal data is reliable at block-build time, EVM discussions are noise. Nail this first. Agenda - L1: Evaluate “graft temporal data to normal tx” path (L1 team) - Verify data availability at block-building for ordering - Produce PoC + benchmark vs manual store (30% code reduction target) - Deliver: PoC + write-up + pass/fail on viability - L1: Fix tx metadata lifetime bug (L1 team) - Reproduce, patch, regression test - Deliver: green test suite + storage lifetime doc - EVM: Execution ADR (L1 team) - Compare Frontier fork vs “revive” vs hybrid; include maintenance burden, gas accuracy, performance, Polkadot compat - Deliver: ADR-001 with decision recommendation - Timing/Validators: Acceptance spec - Define drift windows, signature format, validator evidence rules, minimal population safety - Deliver: Spec v0.1 + test plan - Apps/Processing: Public docs + SDK skeleton (devops lead) - Publish cost-tracking API, function interface, vault config template, partner posting example flow - Deliver: README + sample workflow + test harness - Mobile/Edge: Light-client scope (devops lead/ L1 team) - Define “Roko client” MVP on phones: time sync agent, tx gateway, GNSS + enclave usage - Deliver: 1-pager + dependency map - Grants: Polkadot (advisor) - Schedule with Polkadot; prep 1-pager and 6-slide deck tied to partner + Polkadot deliverables - Deliver: Deck + call on calendar KPIs We’re Driving - L1 correctness: 100% tx-temporal metadata availability during block-build in localnet tests. - Code simplification: ≥30% reduction in custom metadata plumbing if “graft” path adopted. - Timing performance: Quantified drift target vs NTP (define this week) and pass in bench tests. - Processing economics: Cost per function call (CPU, mem, I/O, tokens) surfaced in logs + pricing table for 3 reusable components. - Grants: 1 Polkadot intro scheduled + 1 deck delivered this week