Zingo! Onward

Community Grants Applications
43

This seems like a good idea to me. Match hardware and seed, to get apples-to-apples benchmarks.

2 Likes
44

Hiya @Dodger !

Thus far coordination has been on discord, and github, and now it’s happening here!

Given that zcashd is being deprecated, ZingoLabs Vermilion needs to stop wasting development time on it ASAP.

We chatted with some folks on discord and they offered that we were welcome to do the work necessary to resolve the “add regtest support” issue, which gives us the functionality we require to test zingolib against zebrad.

For @ElectricCoinCo it seems plausible that checking the parity between zebrad and zcashd in the “rpc-tests” will be quite useful in the process of deprecating zcashd. This means we believe that this work is likely to benefit ECC developers who are deprecating zcashd.

In short we think this is a win-win-win, and given that zebrad developers have not told us that it’s a top-priority for them, we have commenced development.

We’re also keeping a close eye on the recently active zebra-grpc code since it’s quite close to what we call a zingo-proxy. We’re not sure what it is/will-be, and we need to land regtest mode before worrying too much about the details of the grpc interface.

Obviously the implementation of a grpc interface to zebrad is adjacent to our nym work, so we’ll need to either implement-or-understand an appropriate grpc server at some point. We’re not precious about who implements the server… we just don’t want to re-invent any wheels/duplicate effort.

2 Likes
45

What tool produced the image that you took this screenshot from?

2 Likes
46

Hi, just to resurface this request for info. We’d like to use a tool like this if we can.

47

It is called browserstack.com

3 Likes
48

Browserstack is great! I used to use it to cross-browser check all the websites I built before launching. The old z.cash and electriccoin.co sites definitely went through plenty of browserstack testing.

2 Likes
49

Hi folks I wanted to offer a quick update on the state of progress on this milestone.

  • ZIP317

    This work is in progress (and will include TEX support).

  • new wallet UI, and streamlining to integrate Nym privacy into the wallet (this does NOT include necessary work on the server-side, or Rust library components, which must be funded by other sources)

    The UI has been extensively upgraded, we will include Nym polling for this milestone.

  • coordinated work with the Zcash Foundation to produce a pure Rust, backwards compatible alternative to zcash/lightwalletd

    We kicked off this work with the substantial strides in both zingo-proxy and our contributions to regtest-mode for zebrad.

  • regtest mode implementation in zebrad to facilitate deprecation of zcashd

As mentioned we have contributed to this work, but won’t be able to complete it without input (which is forthcoming!!) from the zebrad team.

  • Android Background Sync in Android Mobile Devices
  • iOS Background Sync in iOS Mobile Devices
  • an upgraded Basic (Even More Basic) Mode to facilitate new User on-board
8 Likes
50

hey im bit confused.
are the crossed out things done things in list
or the things not crossed out are done? :smiley:

i guess crossed out are done now.

1 Like
51

If it’s crossed out, it’s done.

1 Like
52

What’s NOT done is:

  • ZIP317 (and ZIP320, which we will not land for this milestone)
  • Nym UI integration
3 Likes
53

Hey folks! Quick note, we’re wrapping up last bits of the release. Several of us are out for vacation/illness so the release is anticipated to be mid June!

It’s a significant upgrade, details soon.

8 Likes
54

so soon new update with zip317 correct fees? :eyes:

4 Likes
55

Zingo Labs Vermilion is announcing Zingo 1.4.2, with PTFM!

(And then poofing out of existence, as Zingo Labs are wont to do… but don’t worry Zingo Labs ${NEW_COLOR} is already emerging!)

That’s right PTFM… the “Proportional Transfer Fee Mechanism”.

Perhaps you’ve heard of it by its “ZIP nym”, ZIP317.

I mention it up front, because it ensures that Zingo! operates efficiently in the 0 unpaid actions environment that Zebrad is now enforcing on mainnet.

If that doesn’t mean a lot to you, then just know that your Zingo! transactions will be accepted by Zebrad because we are paying the standard fees. You may have noticed some transactions failing to complete in the last few weeks. If that’s the case, then please try again with the latest version of Zingo!

BUT… that’s far from the only feature, and it’s not really the thing I am most excited about.

When Zingo Labs decided to take over from the abruptly abandoned ZecWallet during the NU5 upgrade, we did so because we believed that was what the community needed (because all of a sudden our wallets stopped working!). But we’d been exploring the space already, and we already had a vision.

From the beginning we believed that Zcash was fundamentally about cooperation.

A new way for consenting people to come together and thrive, without the permission of any authority. To us the fundamental metaphor of the blockchain is not “transactions”, but “collaborations”. Every transaction implies a side-channel connection, a context for cooperation.

That’s what we’ve always intended to build, this coherence of intent is why we’ve been so consistent, why our Path is unwavering. A brief glance at our history shows us building first the necessary foundations:

  1. NU5 transaction parsing
  2. Orchard transactions
  3. sync enhancements (ShardTree and Background Sync, thanks @Honza !)

Then to collaboration tools atop them:

  1. Address Books
  2. Finsights
  3. Basic and Advanced modes, so both the Super Hacker, and their less technical friend can participate.

Now new features aligned with our goal of facilitating a radical diversity of collaborations:

  1. The ValueTransfer, the thing that’s smaller than a transaction, but larger than a note. The thing that Users care about… how much value was transferred to whom.
  2. Support for Portuguese and Russian
  3. Notifications when sends confirm.

Novel mechanisms for supporting us:

  1. Tipping, Zennies For Zingo that sends us 0.01 ZEC per transaction. This gives us a lot of insight into usage patterns of a certain class of users, and incentivizes us to make sending transactions easy.
  2. A simple donation, send us some ZEC!
  3. Vote for Nym, give us some idea of how the community feels about prioritizing Nym network privacy.

And what’s next:

  1. ZIP320 TEX support
  2. More Nym-ness
  3. Hardware wallet support with ZonDax
  4. FROST support with the ZF

This direction, to the Real Private DAO, via an intuitive FROST supporting interface for distributed control of a Zingo Lab fund pool, has been our long term goal since before ZecWallet vanished. We’re continuing on this trajectory which is the trajectory dictated to us by our Users… i.e. us.

And speaking of collaboration, it’s important to recognize just how much of it there is across the groups in our community. @Honza (who I mentioned before) isn’t a Zingoista! (Unless he says he is, in which case I apologize for my error). He is an ECC engineer and his work is why we have Android Background Sync. We couldn’t focus on our collaboration interface, without the collaboration of many groups. Thanks to @Honza and the ECC for all the hard work they’ve done to support us. When they first starting focusing on pushing Zashi into User hands, I was a bit grumpy, but now I am seeing just how much space there is that we need to explore. I am grateful we have fellow travelers helping to chart the future.

19 Likes
56

Congrats on release zip 317.
However, I think it is not a good idea to give new names to protocol rules.
It will confuse users into thinking something is different when the wallet is simply implementing the logic required to work within zcash. Even more so, when the rule is more than a year old.
It would be like saying, for example, “wallet with digital coin transfer and balance maintenance”.

Thanks for your continued support of zcash.

1 Like
57

He’s not renaming anything; that’s the published title of the ZIP: ZIP 317: Proportional Transfer Fee Mechanism

6 Likes
58

oooh! My bad.

1 Like
59

LOL… in @hanh 's defense I am quite fond of scondrelling new words, and terms.

2 Likes
60

And we love you for it :heart::joy:

1 Like
61

Awesome to see progress here. Most excited for FROST and hardware wallet support. :zebra: :shield:

2 Likes
62

@Danika @Dodger

ZingoLabs Considers it’s MileStone 3 obligations complete.

There are two deviations from the original work description where we implemented an alternative feature that fulfills the original intent.

These are:

(1) Even More Basic Mode:

The history tab used to show a list of transactions, but what if there were multiple notes in a transaction? Should we expose a list of notes?

Instead we developed (refined) our ValueTransfer concept which is the set of outputs in a transaction that are sent to a single receiver. This abstraction is what a User needs to see when they are tracking where their money has been sent. In the new interface the History is a list of ValueTransfers that provide the Basic User with the information that they need.

We had considered a Mode that displayed different information, but the properly refined (not by me) ValueTransfer concept proved to be a more elegant and general solution.

(2) Regtest mode in Zebrad:

We contributed significantly to this effort in collaboration with the Zebrad team. As the project owners (and Pull Request mergers) they outlined which code they would accept from us, and which parts they would take the lead on. I believe that we completed our part of the work in May. I believe that the complete feature is either done, or imminent. Either way our contributions are complete.

Complete without amendment and as originally planned:

  • Android BS
  • iOS BS
  • ZIP317
  • Unauthenticated Address Book
  • Customizable Biometric Screen Lock

Additional work not in the milestone:

  • Russian
  • Portuguese
  • Many, MANY bug fixes
  • Chain-Generic Test Harness
  • Rust implementation of lightwalletd
  • POC proxying of transaction broadcast over Nym
  • POC dust-fee handling
  • upgrades to and refactor of sync engine
  • upgrades to display of transaction information in zingo-cli (transaction_details)
  • adjacent work in the vibrant ZLE community including expanding workshops in multiple LATAM zones
  • initial collaborations on infrastructure upgrades
  • the list goes on… to be honest I have trouble keeping up with all the ZingoLabs activities.
11 Likes