Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Second generated UA are not persistent in blockchain. #556

Open
juanky201271 opened this issue Oct 3, 2023 · 3 comments
Open

Second generated UA are not persistent in blockchain. #556

juanky201271 opened this issue Oct 3, 2023 · 3 comments

Comments

@juanky201271
Copy link
Contributor

I created a second address, like this: new tz (UA with 2 receivers)

(main) Block:2248606 (type 'help') >> addresses
[
{
"address": "u1fzsqmxuczdrdcuu7ske7z037xtwsdqcm9gfpmqqvwfvqg596rtl9mff6dz6l4n82wq3l33e4und4uwu6y0yex23cpm8et0ehphgyjflmusmpf7up5mlasxlyd49tft576fjj2q337m5cjdq9njync7pdc25e8f6zmrytklsjz9gj4hw9u2cyv6ykqgnxrup9wxq0chqqfr07ycvtwva",
"receivers": {
"transparent": "t1brEBAzVJvXCySDieJ28kE3PFfvdXBSESD",
"sapling": "zs1mzhhxvwmd9z5v6kdjmd8yyark9ty4sh69m6vwclkhkahkqf6vr84lsfl7ne6s8jn4yn6zm6deh3",
"orchard_exists": true
}
},
{
"address": "u1w8d46ckna89avh0pkuss88ry47xkn9868cdwsw4cytqnj7uku0w9t63jvwr270vlfj8pn3k0agt3v9wrmzusk5r48cd9xyu3e00m4fa35x4sukp7m77yzzz3uquav8wlgdpms0gql04",
"receivers": {
"transparent": "t1VUPANx72a1KqZRaoJzQqiYXYTXQCaNkPd",
"sapling": "zs1tkre9a44x2j3wnuku2uxtf5e3ly8h0yzfg3sgj230t2r6ej6nrfvg0qwvt4jdzge6fa4kdex4ve",
"orchard_exists": false
}
}
]

And I sent some to the second transparent address: t1VUPANx72a1KqZRaoJzQqiYXYTXQCaNkPd
I can see the tx with list...

{
"block_height": 2248596,
"unconfirmed": true,
"datetime": 1696344446,
"txid": "2c9a42403e856a892b6690d658d255ee51beb18ed7dbc7bd3db3dce8c7840d71",
"amount": 1000,
"zec_price": null,
"address": "t1VUPANx72a1KqZRaoJzQqiYXYTXQCaNkPd",
"memo": null
}

Control + C
cd wallets
rm .\zingo-wallet.dat
cd ..
.\target\release\zingo-cli.exe --seed "drive ....................." --birthday 22...... (I waited for synced)
The second address is gone:

(main) Block:2248609 (type 'help') >> addresses
[
{
"address": "u1fzsqmxuczdrdcuu7ske7z037xtwsdqcm9gfpmqqvwfvqg596rtl9mff6dz6l4n82wq3l33e4und4uwu6y0yex23cpm8et0ehphgyjflmusmpf7up5mlasxlyd49tft576fjj2q337m5cjdq9njync7pdc25e8f6zmrytklsjz9gj4hw9u2cyv6ykqgnxrup9wxq0chqqfr07ycvtwva",
"receivers": {
"transparent": "t1brEBAzVJvXCySDieJ28kE3PFfvdXBSESD",
"sapling": "zs1mzhhxvwmd9z5v6kdjmd8yyark9ty4sh69m6vwclkhkahkqf6vr84lsfl7ne6s8jn4yn6zm6deh3",
"orchard_exists": true
}
}
]

And the tx is gone as well.

In order to see again all of these missing data... I need to run again the same new tz command, then rescan and voila... the tx is back & the balance as well, and obviously the second address is the same again.

This is related with this: zingolabs/zingo-pc#117

@AloeareV
Copy link
Contributor

AloeareV commented Oct 3, 2023

Ahh...any shielded funds will be recovered regardless, but the transparent funds not showing up is a problem. It's expected behavior, but it's unintuitive and I suspect very concerning to anyone who runs into it and doesn't know the technical details of how the transparent chain works.

@zancas
Copy link
Member

zancas commented Oct 4, 2023

We need a solution for this, but I don't think we want to prioritize it for this release, do we?

@juanky201271
Copy link
Contributor Author

We can work on this after the release IMO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants