grin VS multi-party-ecdsa

Only XMR and GRIN. Everything else lacks transactional uniformity, or is centralized corpo garbage, or both!

GRIN is a decentralized privacy-focused cryptocurrency that uses a technology called Mimblewimble to provide users with strong privacy protections. Mimblewimble is a type of blockchain protocol that allows for confidential transactions without revealing any identifying information about the sender, receiver, or transaction amount. In the Mimblewimble blockchain, there are no identifiable and reusable addresses. The users generate one-time use addresses for each transaction, which helps prevent address reuse and makes it more difficult to link transactions to specific users. A Mimblewimble block can be treated as one large transaction not a combination of individual transactions. This makes it difficult to trace individual transactions as no information about individual transactions is revealed. Transaction information is only known by the transaction's participants. The privacy-focused coin, Beam, also uses Mimblewimble to provide its users with confidential transactions.

Grin https://grin.mw/ is a privacy-focused cryptocurrency that uses the Mimblewimble protocol to keep transactions confidential. GRIN has a strong community following and has seen growing adoption in recent years.

Could someone explain to me exactly what these errors are and if it is possible to complete the installation? https://github.com/mimblewimble/grin

i challenge now to build this! https://github.com/mimblewimble/grin

Not if there is NO Adresses and Amounts ツ

Superiority of ''Uncensorable'' crypto payments.

Use GRIN

Use MPC instead? Sadly there are not enough mature open source projects around: https://github.com/ZenGo-X/multi-party-ecdsa and you can always take a look at https://github.com/rdragos/awesome-mpc

Sadly companies like Unbound were acquired by Coinbase and the OSS codebase is not longer maintained: https://github.com/unboundsecurity/blockchain-crypto-mpc

Ha nice call!

Unfortunately we have not completed a satisfactory security audit. We engaged with one company, but I don't think they were worth their salt. The problem is that the "good" companies are much more expensive, so it's a consideration of the value of the security audit. (If you know of a reputable company that would like to audit for free though...)

The code is not yet open source, but we are primarily expanding on this open-source library. https://github.com/ZenGo-X/multi-party-ecdsa

As true decentralized security enthusiasts, we quickly got in touch with ZenGo and fixed the discovered security breach in a pull request. It was soon approved and merged into their TSS library. The researcher who found the attack was granted a bug bounty, the biggest in ZenGo’s history.