Qu4nT-X | 1000X GEM

BTC & ETH & XMR Long Holder

[Qu4nT-X | 1000X GEM @Qu4nT_X]

参加D哥的1000xgem挑战,历时4个月,终于从10s玩到510s
最终: 违反规则 被取消资格了 有点遗憾~

[青十五 @mev15_eth]

HFT延迟降低两个数量级的行业通用解决方案要点：
- 核心管道完全避免内存分配
- 绕过Linux内核，走网卡API进行io
- 绕过网络栈，走本地IPC进行内部通信

[Qu4nT-X | 1000X GEM @Qu4nT_X]

no pyo yet. still somehow carrying the whole office.

officially clocking in at pyo street this friday (｡•̀��-)✧

get your worker card: https://t.co/BAnxdLAOLl
@pyopyopyo410

[brucexu.eth @brucexu_eth]

https://t.co/xwk6ND6bTs

[Qu4nT-X | 1000X GEM @Qu4nT_X]

@feikerwu @0xPoseidon_sol 拉一下 谢谢

[Qu4nT-X | 1000X GEM @Qu4nT_X]

@0xPoseidon_sol @gambleking8888 有群了吗 拉下一起交流

[seaify @seaify1]

eth 大约占据我仓位的38.8%, 所以搞了个eth的分析页面

发现，还是有些有趣的点

1. eth 的通胀率只有0.8 % ，最近1年的, 非常低了，其实和btc的通胀持平，对比各国cpi/m2的话，非常友好了😄

2. eth基金会的持仓很低, 仅占供应 ~0.085%（14 个地址 · ~$270M）, 其实它和BitMine 比，啥都不是了，更多是情绪问题

3. eth的燃烧比例太低了，主网 + 二级的那种blob 叫做不叫好，力度太低了，曾经咱也是一直盯着几百gas, 几千gas 发交易的，挺有意思的，再也没有贵族链的说法了

eth似乎以一种降价的���式，正在成为一个结算链，让更多二层活跃的去使用.

另一方面，个人认为, evm系，还是取得了非常大的成功，美国那边最有影响力的coinbase用的是base 二层，robinhood同样用的是基于arb的，都用的eth

然后流动性最好的其实是bnb，也是evm系

现在的sol，根本不再是高速链了，robinhood 0.1 秒，base本质上是0.2 秒，bnb 0.45 秒，arb 好像0.3 秒左右，都比sol强了

非常有意思，eth不再是贵族链，sol同样不再是高速链, 币圈的变化太快了

https://t.co/3rBhLZujex

[Qu4nT-X | 1000X GEM @Qu4nT_X]

@Fried_rice 好吓人

[Qu4nT-X | 1000X GEM @Qu4nT_X]

@dan326714 大佬太牛逼了

[Qu4nT-X | 1000X GEM @Qu4nT_X]

@zh798_btc @jingjue2969 傻逼

[Qu4nT-X | 1000X GEM @Qu4nT_X]

@zh798_btc @jingjue2969 自己去看github更新日志吧

[Qu4nT-X | 1000X GEM @Qu4nT_X]

@opsat_io @Huaguibtc @mork1e @gabe_subfrost @judoflexchop

[Qu4nT-X | 1000X GEM @Qu4nT_X]

@0xbyin 我已经关了半年多了 哈哈

[Qu4nT-X | 1000X GEM @Qu4nT_X]

参加D哥的1000xgem挑战,历时4个月,终于从10s玩到510s
最终: 违反���则 被取消资格了 有点遗憾~

[Qu4nT-X | 1000X GEM @Qu4nT_X]

@VittoStack how can I join ?

[Jonathan @solidsnakedev]

The signing math

When you sign a message with Ed25519, two values get published on-chain as your signature: R and s.

They're computed like this:
- R = k · G (k = the secret nonce, G = a fixed public point)
- s = k + H(R, A, M) · a

Where:
- k = the nonce (must be secret)
- a = your private key (the thing that must never leak)
- A = your public key
- M = the message (transaction)
- H(...) = a hash anyone can compute from public data

(Simplified, the real scheme works modulo the curve order and the nonce is derived from a secret value inside the seed, not the raw seed. But the shape below is exactly what matters.)

Both R and s are public. They're literally in the signature on the blockchain.

Now solve for the private key

Look at the second equation and rearrange it:

a = (s − k) / H(R, A, M)

Everything on the right side is public except k, the nonce. So the only thing protecting your private key a is that nobody knows k.

That's the whole game. Secrecy of k = secrecy of your key.

What SecondFi broke

Correct Ed25519 derives the nonce from a secret:

k = H(secret_seed, M) ← depends on something private

You can't recompute k, because you don't have secret_seed.

SecondFi instead did something equivalent to:

k = H(M) ← depends ONLY on the public message

Now anyone reading the chain can:

1. Read the transaction M → compute k = H(M)
2. Read s and R from the signature
3. Compute H(R, A, M)
4. Plug into a = (s − k) / H(R, A, M) → recover the private key
A toy numeric walkthrough

Forget elliptic curves; use plain arithmetic to see the shape.
Say:

- Private key a = 7 (secret)
- Message hash H(R, A, M) = 3 (public)
- Nonce k = 5

Then the published signature value is:
s = k + H·a = 5 + 3·7 = 26

Good system: an attacker sees s = 26 and H = 3, but not k. Two unknowns (k and a), one equation unsolvable.

SecondFi's system:
the attacker recomputes k = 5 from public data.

Now:
26 = 5 + 3·a → a = (26 − 5) / 3 = 7

The private key falls right out. One signature, no guessing.

Why this beats classic "nonce reuse"

The famous bug, the one that broke the Sony PlayStation 3 and some early Bitcoin wallets, was reusing the same k across two different messages. That took two signatures to cancel the unknowns and solve.

Here you need only one, because k isn't unknown at all. It's computable from data already on chain. Every single transaction a user ever signed is a standalone leak of their key.

The fix was never "understand the curve math." It was "don't be the one writing it."

Libsodium and noble/ed25519 are good examples: both open, both audited, and both give sign() no parameter to supply the nonce.

[Qu4nT-X | 1000X GEM @Qu4nT_X]

@runes_leo 有地址走矿池渠道的 只要是那个矿池出块 他就是1sats包中。

[Miles @zmzimpl]

最开始还没看懂这张图🥹 现在懂了

[rashmor @rashmor_eth]

🧵/1
There are already multiple free AI auditors for smart contracts

But there are almost none focused on blockchain / DLT systems themselves: clients, consensus, execution, bridges, mempools, state sync, resource accounting, and protocol logic.

I spent 7 weeks worth of ChatGPT Pro 20x tokens building DLT Auditor v1

Now I’m sharing it for free: https://t.co/905WCfCBvc

[Qu4nT-X | 1000X GEM @Qu4nT_X]

@krakenfx_ZH 幸运之神能不能降临到我身上

[RWP IV @judoflexchop]

The v3.0.0 Alkanes release runs in metashrew v10.0.0 and optimizes down the stack, approaching a theoretical limit of performance.

The debate today among core contributors to Alkanes resulted in [8:dead] making it into v3.0.0. Activation block still TBD, but soon!