Peeps by @catallacticised
Showing page 1 of 1 (15 peeps total)
Replying to @catallacticised (0x35293f45d559487d9e8a26aa8bd06f84a38f3929)
We will then apply a 6000-minute verifiable delay function, as well as 2⁴² rounds of SHA256 hashes to that value to obtain a random beacon, which we will use to start the ceremony for Semaphore's Groth16 zero-knowledge circuit. https://github.com/appliedzkp/semaphore-phase2-setup
Replying to @catallacticised (0x35293f45d559487d9e8a26aa8bd06f84a38f3929)
The Semaphore team will start phase 2 of its circuit-specific multi-party trusted setup very soon. To do so, we will first use the hash of block #9619000 of the Ethereum mainnet (which should be mined on 6 March 2020 around 1pm EST). http://etherscan.io/block/countdown/9619000
We will then apply a 6000-minute verifiable delay function, as well as 2⁴² rounds of SHA256 hashes to that value to obtain a random beacon, which we will use to start the ceremony for Semaphore's Groth16 zero-knowledge circuit. https://github.com/appliedzkp/semaphore-phase2-setup
The Semaphore team will start phase 2 of its circuit-specific multi-party trusted setup very soon. To do so, we will first use the hash of block #9619000 of the Ethereum mainnet (which should be mined on 6 March 2020 around 1pm EST). http://etherscan.io/block/countdown/9619000
1 Enso
The please-send-ETH scammers are getting creative! Note that 419 scams like this are deliberately designed to filter out people who can spot them.
Just wrote a deep-dive technical analysis of two ERC20 token exploits that happened this week: https://cryptojobslist.com/blog/two-vulnerable-erc20-contracts-deep-dive-beautychain-smartmesh
Replying to @catallacticised (0x35293f45d559487d9e8a26aa8bd06f84a38f3929)
I believe the Peepeth smart contract only stores the IPFS hash. See this tx for example: https://etherscan.io/tx/0xe6bcc760c5768f086bdda2c83aa098a780c8f4f8c08825d44533eb7f2e6b2d60 and click on "Convert to ASCII" to view the IPFS hash.
Oops. I take that back - judging from the input data to the transaction I linked, all I can say right now is that the SC may or may not store the IPFS hash, but it certainly doesn't store the full content of the peep.
Replying to @spengrah (0x26521ede6e1796c6faee57cbc68a178e78d8e23e)
But that would require a change of the peepeth smart contract to store the IPFS hash of the content instead of the content itself, right?
I believe the Peepeth smart contract only stores the IPFS hash. See this tx for example: https://etherscan.io/tx/0xe6bcc760c5768f086bdda2c83aa098a780c8f4f8c08825d44533eb7f2e6b2d60
and click on "Convert to ASCII" to view the IPFS hash.
Replying to @spengrah (0x26521ede6e1796c6faee57cbc68a178e78d8e23e)
Could you consider this a loophole that ethereum might want to close? My understanding is that miners still need to store the information, but they’re not being reimbursed for that storage with gas. If ethereum changes that, could be a risk for contracts with this architecture
If miners/nodes don't store the data, IPFS can do so. If my understanding of the Yellow Paper is correct, the transaction signature can be used for authentication.
I believe that the next wave of awesome dApps will have integrations front and centre. Just imagine if Peepeth had:
- Tips in stablecoins like DAI, rather than in volatile ETH
- One-click ETH-DAI trades via an 0x-based DEX
- Identity management and quick onboarding via uPort
Replying to @matthewcarano (0x8bcfaca5f63c79af77fe4667c7bdb7cbdc7776af)
Is there another way to achieve censorship resistance besides decentralization? I can't name it. Censorship is only possible where centralized institutions exist.
Privacy through strong cryptography. A good example is how Signal uses domain fronting to circumvent censorship even via centralised traffic mediums: https://signal.org/blog/doodles-stickers-censorship/
crypto is 24/7 but a healthy sleep cycle is priceless
It's really ironic how decentralised, Ethereum-based Peepeth is gaining traction, while the @Bitcoin Twitter account gets tossed about in inexplicable and centralised shenanigans.