safe-smart-account VS rust

Recently, I had a chance to work on an interesting task where I needed to integrate the Gnosis Safe multi-signature wallet into the existing application.

Resolv's Protection Protocol™ would implement the highest level of security on all fronts. Our multi-sig wallet is created using Gnosis Safe's industry-standard infrastructure. The keys for said wallet would be distributed amongst the most trusted players in the space (i.e. Kleros, Polygon). This is done so that no one party has full control over the custodian wallet holding everyone's assets. As a result, our customers can rest easy knowing that not one person could run away with the entire pot. We'd also use AES 256-bit encryption to make sure user data is kept safe and inaccessible by third parties.

Prefer self-custody. If you don't feel comfortable, then start with small amounts on a trusted CEX (Coinbase eg.) and then move to self custody. A wallet should be open-source, audited, offers security bounties, is Battle -tested and easy to use. For small funds, use metamask. For big funds use hardware wallet, https://airgap.it (with old Smartphone/device) or a smart contract multi-signature wallet (https://safe.global).

There is the exception of https://safe.global though.

Here a few links in case you want to try out some different wallets: * https://safe.global * https://metamask.io * https://trezor.io * https://onekey.so * https://keyst.one

But if you insist, you can use https://airgap.it or http://safe.global. There the company influence is much less

Self-custody on https://safe.global wallet. Safe Wallet is the gold standard for large funds on EVM-compatible chains. It's audited, open-source, bad bounty programs, battle tested, supports virtually all defi and has multi-sig. What more to you want? Ah, did I forget to mention, that it is formally verified and had the correctness of the smart contract code proven? 😎

If you're only holding coins and not moving them frequently, then a paper wallet might be good. Just generate your seed phrase and address in an air-gapped device (e.g. old phone) and send ETH to that address. If you want a bit more flexibility of usage you can use https://airgap.it or an hardware wallet such as Trezor, Keystone or OneKey. And the ultimate gold standard is to use a Safe Wallet (https://safe.global). It's a multi-signature wallet and is even formally verified to be correct. It's the best choice atm.

Or even better just https://safe.global for a secure, audited, formally verified, battle tested and open source smart contract multi-signature wallet. It has arguably the best security guarantees you can have atm.

> There are online Rust compilers and interpreters already if you just want to rapid prototype and develop ideas in Rust

You are responding to one of the key developers of Rust early on[1], who's been working with the language for 14 years at that point.

[1] https://github.com/rust-lang/rust/graphs/contributors?from=2... and he's still #16 in commits overall today, despite almost no activity on the rust compiler since 2014.

If you haven't dipped your touch-typing fingers into Rust yet, you really owe it to yourself. Rust is a modern programming language with features that make it suitable not only for systems programming -- its original purpose, but just about any other environment, too; there are frameworks that let your build web services, web applications including user interfaces, software for embedded devices, machine learning solutions, and of course, command-line tools. Since a custom GitHub Action is essentially a command-line tool that interacts with the system through files and environment variables, Rust is perfectly suited for that as well.

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.