Blockchain Wizard

Cybersecurity Student, Smart contract developer, Green heart hacker💚

[Blockchain Wizard @smart_contrac]

@ukaohacc Massive

[Elon Musk @elonmusk]

True

[Blockchain Wizard @smart_contrac]

@cyb3rshi3ld Hi
Started already learning

[Blockchain Wizard @smart_contrac]

@ebimoses40 Congratulations brother

[Blockchain Wizard @smart_contrac]

@bil0090 @cgtwts 😂😪

[Blockchain Wizard @smart_contrac]

Benefits of Ai and Blockchain

[Blockchain Wizard @smart_contrac]

Can you share your vision for the future of artificial intelligence and Blockchain and its potential applications?

I would love to hear to views in the comments

[Blockchain Wizard @smart_contrac]

@bil0090 @karthikponna19 Why 😭

[Blockchain Wizard @smart_contrac]

@_vielite_ @xyz_remedy Congratulations bro 👏

[Blockchain Wizard @smart_contrac]

How's everyone https://t.co/XSHkT2hXbF?

[Blockchain Wizard @smart_contrac]

@bolacrypt__ @BolaCrypt Alright @bolacrypt__

[vitalik.eth @VitalikButerin]

And my personal focuses (and non-focuses) for 2025. Should be predictable from things I've done and written, but it's worth re-stating explicitly.

[vitalik.eth @VitalikButerin]

We can also simplify the protocol by making sure that sub-protocols are shared as much as possible: there should ideally only be one way we do X, across the consensus, execution and other layers. Potential targets: erasure coding, serialization, trees.

[vitalik.eth @VitalikButerin]

Privacy was always the true alpha.

[vitalik.eth @VitalikButerin]

A fun math aside, on the idea of splitting a large zk proving workload between multiple provers.

Suppose you have N provers, and you have a proving workload that you split into N parts (so, one part per prover). You require provers to pre-register, but registration is open-access.

Suppose you have a constant fault rate (eg. 1/5 of registered provers fail). Provers expect to complete in one round (eg. 3s). If one prover fails, other provers have to come in and re-prove that load. How many rounds does it take for the entire workload to get proven?

Answer: log*(N)

(yes, that's the iterated-log function)

Why:

In the first round, you go from N unproven workloads to N/5 unproven workloads

In the second round, each remaining workload gets assigned 5 provers, so per-workload failure rate becomes 1 in 5^5. So you go to N / 5 / 5^5 unproven workloads
In the third round, each remaining workload gets assigned ~5^5 provers, so failure rate is 1 in 5^(5^5). So you go to N / 5 / 5^5 / 5^(5^5) unproven workloads

[ICP WIRE @icpwire]

ICP United | E7 | The Decentralized AI Revolution

AI’s future is decentralized! 🚀

Watch this ICP United episode on Caffeine AI, on-chain LLMs & Bitcoin via Chain Fusion—only on the Internet Computer. 👇

[Blockchain Wizard @smart_contrac]

@Asquare012 @ukaohacc