genius!
Over the past few weeks I've gone from thinking leanPCS is total bull to being a total bull. So let me explain some of these buzzwords in more detail.
At the core, 8288 is about hyper-scaling data and execution for any computation that needs to get performed on a piece of data once, the chain learns the answer, and then we never need to see that data again. This sounds very specific, but it includes most "heavy" things happening on Ethereum:
* Signatures
* STARKs
* Merkle branches
* FHE computation
* ...
Really the first two are the most important.
Once we go quantum-safe, signatures get bigger (65 bytes ECDSA -> 1-6 kB WOTS/SPHINCS depending on params) and ZKPs get much bigger (200-1000 bytes with groth16, PLONK, etc -> 128 kB with STARKs). This is unsustainable to put on chain, and 8288 fixes this.
8288 works by aggregating STARKs in the mempool. First, you as a user generate the STARK or SPHINCS signature or PCS opening (more on that last one later), and publish it. Then, each node listens. Each tick, each node takes all of the new objects that it has seen, and generates a STARK containing a list of "claims":
"pubkey P has signed message M"
"program X run on data D has output Y"
"p(X) = Y for some polynomial P whose hash is H"
and a proof that it has seen a signature, STARK or PCS opening verifying those claims. So the only information getting re-broadcasted is:
(i) hashes of inputs and outputs (~64-96 bytes per claim)
(ii) a single STARK proof per tick
These aggregate proofs themselves get re-aggregated, and eventually you get to a single "master proof" in the block, that verifies that all of those statements are true. And so the only other data that has to actually go on chain is the statements (the (P, M), (X, D, Y), (X, Y, H) tuples I described above), not the actual signatures or proofs. This gets put into a specialized frame type.
Now, let's get into the leanSPHINCS vs leanSTARK vs leanPCS part.
The core distinction is: *what is the underlying object that the user is creating?*
In leanSPHINCS, it's a signature, and specifically this particular type of purely-hash-based signature: ethresear.ch/t/sphincs-minus…
If we add leanSPHINCS, then users will be able to make quantum-safe accounts, and pay only a little bit of gas (4096 for the 64 bytes) for each signature. So we get scalable quantum-safety for regular accounts, multisigs, etc. But it's only one specific signature scheme, you can't do anything else.
In leanSTARK, it's a STARK. This means it's fully general: the user runs whatever computation they want, and publish a STARK of it. So you can use it for:
* Any signature scheme (including eg. lattice-based ones if you like those)
* A multisig that hides its internal logic
* Privacy protocols
* Private account abstraction: authorization logic that depends on some value hidden elsewhere in the state, so you can have one key that controls all your accounts without publicly linking them to each other
Basically, it's a free for all, in the same way the EVM is a free for all.
But leanSTARK has a practical downside. The protocol would have to specify the language in which users write their programs (we call this the "ISA"). So we would have to agree on that language. This is a really big deal - it's the first big case of "Ethereum moving beyond the EVM" - and so it's likely to take time to agree on the details of it, especially since the ISA would be hard to upgrade. There are benefits to taking longer on this, figuring out the ideal ISA, and then even giving access to it inside regular contracts.
LeanPCS is the third option. PCS stands for "polynomial commitment scheme": a proof that P(x) = y. The most important thing to know about PCSes is that they are by far the most important "hard" component of a STARK (see here: vitalik.eth.limo/general/202… ). If you have a "magic PCS oracle" (which from the EVM's point of view, 8288 is), you can verify a STARK in ~20-40k gas.
The most important gain with PCS is that there is far less that we need to choose. Specifying a PCS only requires specifying a field, and there is a natural option: the 128 bit binary field (technically, we can go more general than that, and say the 2^k-bit binary recursive tower field, going up to 256)
LeanPCS is less efficient than leanSTARK onchain, because you would have to put multiple claims to prove one thing. But it's arguably more efficient offchain, because you have much more flexibility to choose proof systems.
But most importantly, leanPCS gives you the same generality as leanSTARK, in a way that could potentially be implemented very quickly. And once we figure out the ISA, we can add leanSTARK later.
So there is a route to getting "the cryptographic proof singularity" much faster than any of us expected, and that route runs through 8288 with leanPCS.
firefly.social/post/x/212092…
55
[绝望求助]🙏🙏🙏
合约赚了34w,账户40w全部被币安无端冻结!
求大家帮我转发扩散。
我真的没想过自己会被逼到这种走投无路的境地。
我一直极其信任币安,觉得作为全球最大的加密货币交易平台,把资产放在这里是最安全、最值得信赖的。但如今突遭美国科罗拉多州地方法院连带冻结,所有的信任瞬间崩塌。
我的本金被卡死不说,凭自己本事在合约里辛苦赚到的34wUSDT、总共40w的合法资产,现在全部被扣、不给提现。如果是某笔资金有问题被扣,不能其他资金也被扣吧。
更让人感到无助和绝望的是整个过程中的推诿:
1️⃣我出于信任去找币安客服,币安要求我提供资金来源,我提供了,然后币安又说他没权限客服直接两手一摊,要求我一个远在亚洲的个人自己去联系美国法院;
2️⃣我按照指引去找法院网站,却发现根本没有任何
普通用户提交防御或证据的公开入口。
我自问所有交易清清白白,每一笔资金都有据可查。但面对这突如其来的跨国冻结和冰冷的机械程序,我真的感到深深的绝望与无助。原本以为值得信赖的大平台,在关键时刻却让我连一个说话、递交材料自证清白的窗口都没有。
恳请各位业内大佬、KOL 朋友帮忙转发扩散!难道普通用户在中心化巨头面前,就只能眼睁睁看着自己合法赚来的血汗钱被强行吞没、求告无门吗?
本文当事人是@Shawn126888 ,请bn的各位负责人来看看,这么搞我也挺害怕的,身边的朋友一起资金也都挺大的,都也担心被冻结及冻结后没法处理。
@heyibinance @sisibinance @yayabinance
解决问题是最主要的,批评也是为了让币安更加强大
感谢同行不眠不休关注我们的产品,不管在安全和产品还是CZ的私人生活上操碎了心,你们的360环评是我们持续迭代的动力,希望你们关心自己的用户像关心币安一样。
对于这位在使用2个独立App转错币的用户遇到问题,于法我们确实没有办法从别人账号直接划款,于情我个人会补贴这份用户打错币的损失。我们会像你在乎币安一样在乎我们的用户。
因为历史合规原因币安有三个本地站点完全独立开发,产品架构和业务形态和币安主站不同,主营本地法币交易。但为了避免类似的情况再出现,下一步我们会在币安支付转账加三次确认。每一次公开的讨论都是我们成功的阶梯,欢迎大家在评论区提出有效的产品建议,我会让产品在评论区选出最好的10个产品建议,每人奖励1BNB,为期一周。
66
币安损失六十多亿的复盘,确实过于离谱,在员工行为管理上一定是除了问题,我都不会去搜索引擎下载编程工具,这是极度危险的,我都知道编程单独用一个电脑,币圈单独用一个电脑,这家伙直接在工作电脑上搞面试下载代码啥的,世界真是一个草台班子呀!
46













