Candle Hunter 📈 Web3 Creator • Builder Building On @arc :- LinkPay

Moon
Joined April 2021
Let Consistency and Discipline Win This Time ⏳
2
203
Arc Docs Notes, Day 2/30. Today's topic from the @arc docs: which logs does a USDC transfer leave on Arc? USDC movements appear in logs from two sources: - The system emitter logs every explicit USDC movement, with 18 decimals. - The ERC-20 USDC contract logs its own Transfer, with 6 decimals, only for ERC-20 calls. So: - Native send: system log only - ERC-20 transfer(): both logs - Contract call with value: system log only - Mint or burn: both Rules for indexers: 1. Count only one log stream. Filter by emitter address. 2. Never mix 6 and 18 decimals. 3. Gas fees emit no log. Derive them from the receipt. Source: Arc docs, USDC events. Which stream do you index: the system log or the ERC-20 log? Unofficial community note. Not affiliated with or endorsed by Arc or Circle.
1
1
100
Has @RaylsLabs been audited, and does the public code match what the auditors found? I read all 3 Halborn reports (42 findings) and checked 8 claims against the Axyl code with a short script. Some details are easy to miss.
1
1
48
Who controls the fee split? [verified in code] Docs and code defaults: 50% validators, 50% burn. But setConfig() is admin-only, with no timelock in it. One call can change the split. The docs say the 50/50 "will likely evolve". github.com/raylsnetwork/axyl…
1
37
What I couldn't confirm [unconfirmed] - who holds the admin role on mainnet - which fixes are in the live mainnet bytecode (I read source) - whether the burn bridging code was audited Docs: docs.rayls.com/docs/public-c… Video: AI voice, code shortened. Checked 25-26 Oct 2026.
9
🚨 $5 FREE BONUS 👀💰 Just got my $5 bonus on @WahooPredict 🔥 If you haven’t joined yet, this is an easy one to check out 👀 Join → Get $5 Bonus Quick signup Start with free bonus wahoopredict.com/bonus?r=Qvv… Don’t sleep on free money 🫡
60
Arc Docs Notes, Day 1/30. Each day for the next 30 days: one new topic from the @arc docs, explained simply. Day 1: Transaction not showing up on Arc? Check your maxFeePerGas first. The docs list a minimum base fee of 20 Gwei. When you send a transaction, you set maxFeePerGas, the most you will pay per unit of gas. If it is below the floor, the transaction is dropped by the mempool silently. That means no receipt and no error, so it can look like the transaction just disappeared. What to check: 1. Set maxFeePerGas to at least 20 Gwei. 2. Gas on Arc is paid in USDC, so the fee is already in dollars. 3. Check the default fee values your library sends (viem, ethers.js or others). Source: Arc docs, EVM compatibility and Fee display. Have you seen a transaction go missing like this? What was the cause? Unofficial community note. Not affiliated with or endorsed by Arc or Circle.
3
8
210
Can you check @RaylsLabs fees and burns yourself, without trusting anyone? I tried with just the public explorer and the Axyl code. Fees and who gets the tip: checked on 7 real blocks. The daily payout and the 50% burn: not yet. Video below. Each claim is labeled.
2
1
104
What I couldn't confirm [unconfirmed] Daily payout to validators: no distribution event on the aggregator in the explorer data (6 logs, no token transfers). System calls may not be indexed. Burn totals: the transparency portal wouldn't show me its numbers.
1
16
I built LinkPay on @arc and it's now LIVE on Mainnet. Testnet ✅ Mainnet ✅ What is it? Pay anyone with just a link. No copy-pasting long wallet addresses. Create a link, share it on WhatsApp, Telegram or X, and they pay. "Why not just use a normal wallet?" Fair question. Wallets work great if you know addresses. Most people don't. A link is something everyone already understands. Perfect for freelancers, creators and small shops. What's next 👇 🔹 Applying for the Arc grant 🔹 If approved, building my own MetaMask-style wallet with payment links built in 🔹 2 more unique features dropping very soon (can't reveal yet 👀) Try it on Mainnet :- linkpay-lilac.vercel.app/ Please start with small amounts while we're early. Honest feedback welcome @silencexlm @samconnerone @bobbilee
5
8
347
Why does deterministic finality matter for settlement? short answer:- a bank needs a moment it can call final. "probably final" is not enough. the bis describes legal settlement finality as the point where a transfer becomes "irrevocable and unconditional" so i read the axyl code behind the @raylslabs public chain and pulled live mainnet blocks to check what "sub-second finality" means in practice every claim below is tagged: documented, verified in code, measured, or unconfirmed 🧵
1
2
129
The part nobody tweets about: deterministic finality has a price. when it breaks, it stops on 21 jun 2026 mainnet halted after a bug at the epoch 52 boundary. the postmortem is in the public repo with the cause and the fix (3a71a1a). all 7 validators froze. it doesn't say how long it lasted credit where due: the postmortem and the halborn audit reports are public and the guarantee depends on who holds the votes. at launch the committee is run by the rayls foundation. with 7 validators, 2 faulty is survivable, 3 is not (my calc) holds up: deterministic commit rule, fork halts the engine, ~1.36s block cadence unconfirmed: sub-second under real load evidence: github.com/raylsnetwork/axyl @1afb0b4, explorer.rayls.com/api/v2/bl…
1
1
31