Ironbelly - Progress update thread (Sep - Dec 2020)

[davidtavarez]

@shush

a user, I’d expect that if I point my front-facing camera at another phone, the two phones would able to communicate by reading each-others animated QA codes. The phones will vibrate to give feedback once the interaction is complete.

Why not NFC as Apple Pay and Google Pay?

[grn]

Cameras are more ubiquitous.

[shush]

NFC would be great for devices that support it. I would develop the QR scanning first and then NFC second. Admittedly, NFC would be the most ideal user experience.

[i1skn]

So, it’s time for another update!

Last couple of weeks I’ve been working on adding Grin addresses to Ironbelly. I’m glad to share with you all that now it’s working on iOS and Android support is coming very soon!
Right now I’m polishing a couple of edge cases and after that is done I will release 4.1.0 with Grin Addresses support for iOS.

Here is a sneak peek: https://streamable.com/s53vgz

[lehnberg]

Nice job, looks great @i1skn!

[shush]

How do Grin addresses work? I’ve not been keeping up. Doesn’t grin require interaction? So how does the address work (is it a tor address)?

[bluimes]

Hey Shush,

Take a look here

0015 slatepack - Grin Documentation

[i1skn]

Hey everyone, it’s time for another update!

As of now both Android and iOS latest versions support Grin Addresses and Slatepack
Besides there is a couple things I’ve packed into the latest release as well:

• Automatic background update of the transactions state, so no need to pull down manually!
• Slightly different unlocking wallet mechanism under the hood, which would allow to speed things up a bit as well as removes the need to store password in JavaScript environment in the upcoming release.
• Android should have a slightly faster Fingeprint unlock mechanism.
• Implemented automatic screenshot taking before each release (Apple rejected a build recently because the screenshots were not up to date)
• And as always minor cosmetic lift-up and optimizations

What’s next?

Here is my current roadmap:

• Bring QR codes for encoding Slatepacks and Grin addresses (should be in the next release)
• Minimize places where sensitive data is exposed to the JavaScript runtime (continue my effort, which I’ve started in the current release).
• Introducing PIN instead of a password, which would allow to increase level of security and create a better UX for unlocking.
• Ability to change PIN

Also, I’m planning to release version 5.x of the wallet with a complete support of the upcoming hardfork on time!

Deprecation note!

After the upcoming hardfork Ironbelly would not support http and file transactions in favor of Grin addresses and Slatepack.

[grin001]

Keep going! Ironberry’s first mobile phone Wallet

[i1skn]

Hi everyone! It’s time for another small update!

While new 4.2.0 version of Ironbelly is rolling out to the stores, I wanted to share that it has full support of QR codes for send and receive using both Grin addresses and Slatepack. Also, QR codes are fully compatible with the new Grin++ Android wallet, so you should be able to transact between these two without problems!

Next stop is improving security and unlocking experience!
Stay tuned, cause we are running a marathon here, not a sprint

[grin001]

The new version is a beautiful mobile wallet

[davidtavarez]

How cool is this?!

Sending $Grin from @ironbellywallet (iOS) to Grin++ mobile( Android) using only QR codes! Grin/MW is so hard to use 😉 pic.twitter.com/MamoDWx4av

— G R I N ツ (@grin_privacy) December 18, 2020

[Anynomous]

This is what I call usability!
What happens under the hood (magic) is irrelevant if sending receiving grin is as easy as scanning a QR code.
This user experience combined with great privacy and low transaction fees makes Grin ideal privacy cash, can’t wait to try this out ‍♂

[i1skn]

Hi everyone! It’s time for another update!

Right now I’m polishing the new release, which you should see in the stores very soon. It’s rather a security/performance release and here is what it will bring:

• Faster transitions between the screens
• Initial sync should be faster as well
• Password/mnemonic is not stored in the JavaScript state
• Send transactions now has Kernel Excess field and link to GrinScan, so you can point it if there is a dispute regarding the transaction being sent or not
• Paper Key screen is now protected by password
• Code is finally completely migrated to TypeScript!

Right after this release hits the stores I will be preparing the next one - compatible with the upcoming hardfork. All users would need to update to it once hardfork is done.

[Anynomous]

Nice security improvements, will the new version also hit the Android store, or for now only iOS?

[i1skn]

For Android as well.

[i1skn]

Hi everyone!

Regarding the upcoming hardfork - Ironbelly 5.0.0 is in review on both App and Play stores, so you all should be able to get it very soon! No actions from users, who use the default Ironbelly node are required. For ones, who use their own nodes, please update them to v5.x to be able to continue use Ironbelly.

More info here: Network Upgrade 4! | Ironbelly | Grin mobile wallet.

P.S.: I’ve been trying to ship Dark mode within this update, but decided to do so as a part of the next update. But here is a sneak peek

[scooter_d]

I keep all my grins in Ironbelly, it is a beautiful wallet.

[grndld]

Hi there! When will URL addresses get implemented to Ironbelly? Every exchange I use supports those only. thx

[markov]

Supprise! There will never be any URL address support hereafter Hard Fork 4. Only tor and slatepack are supported.

Currently, only 1 exchange (and the trading volume is tiny, so bad) implements Tor/slatepack address.