ConsSize @ConsSize

@bigpey You can use the Semaphore protocol to create anonymous claims. It's a zero-knowledge protocol that lets users prove they're eligible without revealing who they are. We built a proof of concept at @modp_ for privacy-preserving claims and membership verification.

1 0 4 489 0

View Details

ConsSize @ConsSize

4 months ago

@secondfiapp Good news! The reported address is where Emurgo has moved the victims' funds away from the hacker. The impact has been significantly reduced to just 16M ADA.

1 0 1 107 0

View Details

ConsSize @ConsSize

4 months ago

The first transaction from the @secondfiapp wallet hacker appears to have been funded by a highly active address. This transaction: cexplorer.io/tx/5f1c9e58b25… funded the hacker address: cexplorer.io/address/addr1q… Does anyone know who controls this address? cexplorer.io/address/addr1v…

6 4 53 223K 5

View Details

ConsSize @ConsSize

4 months ago

@AirdropGlideApp It isn't a Blockchain hack. It's a wallet hack.

1 0 16 753 0

View Details

ConsSize @ConsSize

4 months ago

@WuBlockchain It's 20 million ADA not dollars

0 0 2 163 0

View Details

SecondFi @secondfiapp

4 months ago

As per our previous post: x.com/secondfiapp/st… We have identified the root cause and have since rolled out a patch for all unaffected wallets. This will allow us to resume normal operations soon. ----- Regarding affected wallets, 4 distinct draining events occurred. 3 were executed by external threat actors, resulting in a loss of ~16m ADA across 374 addresses. To prevent total loss during the active exploit, emergency rescue measures were triggered to secure the available ~129m ADA and continues to be routed to an independent, qualified third-party custodian, where they are held securely for the benefit of the affected wallet addresses. An external accounting firm has been engaged for a special audit to independently verify those holdings. We are working to facilitate the verification process so users can claim back their assets safely. Affected users should submit their claim at support.secondfi.io We take this incident seriously and are working to ensure all assets are returned to affected users as soon as possible. As stated, we have identified the root cause, it is at the address level. Please DO NOT RESTORE your recovery phrase into another Cardano wallet, this does not mitigate the security risk. The security risk occurs when an affected user signs a transaction. Further explanation to follow.

SecondFi @secondfiapp

4 months ago

To provide more clarity, we have identified the nature of the incident, it is at the address level. The security risk affects wallet users when a transaction is signed. Therefore recovery to another platform or wallet does not mitigate the risk. 🚨 DO NOT restore your

81 65 172 131K 24

112 144 418 247K 72

View Details

ConsSize @ConsSize

4 months ago

@secondfiapp OMG, if this is true, it would suggest that a private key can be derived from a public key. Cardano addresses don't expose public keys directly only their hashes. A public key is typically revealed only after the first signed transaction.

0 0 0 903 0

View Details

ConsSize @ConsSize

4 months ago

@zippy257 @secondfiapp It's a binance wallet.

1 0 3 154 0

View Details

ConsSize @ConsSize

4 months ago

@agustinenada I think it's 13M or am I wrong?

0 0 1 318 0

View Details

ConsSize @ConsSize

4 months ago

Just to clarify, dynamic Heads already existed through incremental and decremental commits. However, there was still an edge case: if the Head was closed, users could end up unable to withdraw their funds. With Partial Fan-outs, that gap is closed and the dynamic Head lifecycle is finally complete.

0 0 1 44 0

View Details

ConsSize @ConsSize

4 months ago

@NixePool @sharan_konerira @IOGroup Partial Fan-outs solve the problem of having too many UTxOs in a Hydra Head, which can lead to permanently locked funds. They also enable dynamic Heads, allowing users to enter and exit applications such as DEXs.

1 0 0 67 0

View Details

ConsSize @ConsSize

5 months ago

@mr_cata @cardano_govtool BTW, a node in the browser could have solved this. :)

0 0 0 12 0

View Details

ConsSize @ConsSize

5 months ago

@AndreasPletsch1 @TapTools That's a fair point that they are part of the community. I didn't know that they had delegated to other dRep. I don't know how to feel about that. I have a question, is it public who they delegate to?

1 0 0 22 0

View Details

ConsSize @ConsSize

5 months ago

@AndreasPletsch1 @TapTools The FE should either support or abstain. Their funds ultimately belong to the community, and since we can't undelegate, they should let the community decide.

1 0 0 26 0

View Details

ConsSize @ConsSize

5 months ago

@TapTools Emurgo abstained which I think is the correct position

0 0 1 90 0

View Details

ConsSize @ConsSize

5 months ago

@ItsDave_ADA I think Project Catalyst being suspended is deeply connected to this. The treasury proved that developers promoting their work is far more effective at attracting people than any flashy event booth.