JJS

1.7K posts

JJS banner
JJS

JJS

@JJS_OnChain

Web3 Security | TAM @Certora | @CyfrinUpdraft Alumni

United Kingdom Katılım Haziran 2023
608 Takip Edilen353 Takipçiler
JJS retweetledi
Canton Foundation
Canton Foundation@CantonFdn·
The Protocol Development Fund in action. @Certora is building an open-source static analysis tool for Daml, bringing automated, verifiable security assurance to institutions and builders deploying on @CantonNetwork. This is what the Fund was designed for: 5% of all Canton Coin emissions directed toward public goods that strengthen the ecosystem's core infrastructure.
Certora@Certora

Certora has been awarded a grant from the @CantonNetwork Development Fund. We're building an open-source static analysis tool for Daml, bringing the same rigorous, automated analysis we've built for DeFi to institutions building on the Canton Network. More details 🧵

English
3
11
48
2.5K
tpiliposian
tpiliposian@tpiliposian·
we are so excited about this opportunity. personally, as someone coming from tradfi, i am really hyped to see the big boys coming to blockchain
Certora@Certora

Certora has been awarded a grant from the @CantonNetwork Development Fund. We're building an open-source static analysis tool for Daml, bringing the same rigorous, automated analysis we've built for DeFi to institutions building on the Canton Network. More details 🧵

English
2
1
24
1.9K
JJS
JJS@JJS_OnChain·
@0xaudron Nice ser! Great to see more talent like yourself doing new and exciting things!
English
1
0
1
24
0xaudron
0xaudron@0xaudron·
What DAML/Canton has that Solidity/EVM structurally doesn't? 1. Privacy as a language primitive 2. Authorization as a type, not a runtime check 3. Granular three-tier permissions, not just onlyOwner 4. Multi-party authorization required to create a contract 5. UTXO-style immutability, so reentrancy doesn't exist 6. Cross-domain atomic transactions with preserved privacy 7. signatory != msg.sender
English
4
0
23
1.3K
JJS
JJS@JJS_OnChain·
I think the notion of doing security as a checkbox is an issue. Thinking that doing an audit means you’re safe is no longer valid. BBPs are great because it means continuous security but just not guaranteed as you don’t actually know if people are looking at your code or not. So integrating security at any point and on as many layers as possible (smart contracts, opsec, monitoring etc)
English
1
0
1
43
0K
0K@ZeroK_____·
I feel sad seeing all these hacks these days. Sometimes I feel like I’m part of the reason this is happening, even though deep down I know I’m not. What do you think our community should do in this situation? solutions only, I’m not here to hear anything negative.
English
8
1
16
1.6K
JJS retweetledi
Royco
Royco@roycoprotocol·
Why did Royco get multiple audits and formal verification? We sat down with @teryanarmenn from @Certora to break it down. Certora completed a comprehensive audit and formal verification engagement on Royco Dawn, further fortifying its security stack. Watch it now.
English
3
5
37
6.6K
JJS
JJS@JJS_OnChain·
@Raph_Bloch The event was great! Thanks for having me and looking forward to the next!
English
0
0
1
34
Raphaël Bloch 🐳
Raphaël Bloch 🐳@Raph_Bloch·
I’m in London for one more week! Things are moving forward on stablecoins and tokenization.
Raphaël Bloch 🐳 tweet media
English
3
0
19
1.5K
JJS retweetledi
vitalik.eth
vitalik.eth@VitalikButerin·
Many people have claimed that with AI-assisted bug finding, secure code (and hence trustless anything) will be impossible. I have a much more optimistic take, and AI-assisted formal verification is a major part of the reason why: vitalik.eth.limo/general/2026/0…
English
432
383
2.5K
397.6K
JJS retweetledi
Cork Protocol
Cork Protocol@Corkprotocol·
How would the KelpDAO x Aave incident operated in a market integrated with Cork's risk infrastructure? Example: aETH was assumed fully liquid, but the exploit made it illiquid. A live Cork aETH pool would have let holders pay a premium upfront to guarantee exit liquidity at NAV, with that guarantee locked in a smart contract. Priced vs. unpriced risk
English
0
1
14
759
JJS
JJS@JJS_OnChain·
7/ Then why BFT / Super Validators? Because even if the synchroniser cannot read the transaction, it still controls important public facts: 1. What got sequenced? 2. In what order? 3. Before what deadline? 4. Was the final result commit or abort? Those facts need decentralised trust.
English
0
0
0
13
JJS
JJS@JJS_OnChain·
6/ This is the key mental shift: Canton is not hiding a public blockchain transaction with advanced cryptography. It is avoiding the need to publish the transaction in the first place. Privacy comes from selective disclosure plus a shared synchronisation layer.
English
1
0
1
32
JJS
JJS@JJS_OnChain·
You have heard that @CantonNetwork allows its users to have privacy. But it does not use ZK, FHE or any other fancy shmancy heavy computation cryptography primitives. But How? Lets take a look 🧵
English
1
0
4
266

Keşfet

@Certora @CantonNetwork @tpiliposian @0xaudron @teryanarmenn @Raph_Bloch @elonmusk @BarackObama