Wrong key generation from mnemonic about cyb-archeology HOT 39 CLOSED

@PumpkingWok ,
It is okay. Let's work together then and split the money 50-50. This is a bug and it is intellectually challenging. So, come let's reason it together. Shoot a mail to me, my email is in my profile.

from cyb-archeology.

Hi there,
If i can ask it, what is the motivation that bring you to accept the second interest propose ?
Just to know if i was wrong in my application, but i don't see something strange.
Thanks in advance.

from cyb-archeology.

Hi @serejandmyself,
Thanks for the reply, no worries, just to know.
Just to say, the next time you should create a bounty reserved and not open to everyone, if you already know who you want to do work on this.
Enjoy your project !!!

from cyb-archeology.

@mul53
Congrats ... .
I spent time rebuilding the whole log ...go and javascript. I found that they were correct and sound. I was to check the front end.

from cyb-archeology.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 0.3 ETH (65.79 USD @ $219.29/ETH) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $151,001.30 more funded OSS Work available on the Gitcoin Issue Explorer

from cyb-archeology.

@sebastiantf Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

from cyb-archeology.

@sebastiantf Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

Yes I am still working on this issue. I am trying to get to know the codebase a little more.

The Getting Started links in the README returns a 404

Edit: Is this comment enough to prevent being removed from this issue?

from cyb-archeology.

Are the following insights correct:

cyberd cli uses: github.com/cosmos/go-bip39
cyb app uses: github.com/bitcoinjs/bip39

Might there be differences in how both of these libs implement bip39?

from cyb-archeology.

@mrlp4 Can you please verify my findings above so that I could proceed with my work.

from cyb-archeology.

We need @xhipster to reply to you, @sebastiantf.

from cyb-archeology.

Ok. Waiting for his response.

from cyb-archeology.

@sebastiantf sorry for late reply.

Might there be differences in how both of these libs implement bip39?

Might be not. The only thing which need specification is a dereviation path. Our path would match cosmos path with different prefix: cyber

from cyb-archeology.

@sebastiantf Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

from cyb-archeology.

Yes I am still working on this issue

@xhipster Can you please specify where and how the derivation path is being specified in cyberd cli using cosmos. I couldn't find it specified in that repo.

I found the derivation path 44'/118'/0'/0/0 specified in cyb

from cyb-archeology.

Also, why does prefix.go in cyberd cli specifies:

• AccountAddressPrefix
• AccountPubKeyPrefix
• ValidatorAddressPrefix
• ValidatorPubKeyPrefix
• ConsNodeAddressPrefix
• ConsNodePubKeyPrefix

while constants.js in cyb only specifies:

• PREFIX_BECH32_ACCADDR
• PREFIX_BECH32_ACCPUB

Aren't the Validator and ConNode Prefixes required/used in cyb?

from cyb-archeology.

@sebastiantf Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

from cyb-archeology.

I'm having some hard time triaging the bug and I haven't received reply comments that could guide me

from cyb-archeology.

@sebastiantf Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

from cyb-archeology.

I havent been able to triage whats going wrong yet

from cyb-archeology.

I have stopped the work on this bounty as I haven't been able to discover whats going wrong and the time limit is closing down

from cyb-archeology.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Workers have applied to start work.

These users each claimed they can complete the work by 2 weeks, 2 days ago.
Please review their action plans below:

1) igetgames has applied to start work (Funders only: approve worker | reject worker).

I believe I can solve this issue quickly.
2) josh-kean has applied to start work (Funders only: approve worker | reject worker).

I will review all the text content of the mnemonic phrase and then follow the process that the phrase is hashed through. I've built my own implementation of BIP-39 and am familiar with issues that can arrive when dealing with entropy.

Learn more on the Gitcoin Issue Details page.

from cyb-archeology.

@igetgames Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

from cyb-archeology.

@igetgames Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

from cyb-archeology.

@igetgames Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

from cyb-archeology.

@igetgames Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

from cyb-archeology.

@igetgames Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

from cyb-archeology.

@igetgames Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

from cyb-archeology.

@igetgames Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

from cyb-archeology.

@igetgames Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

from cyb-archeology.

@igetgames Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

from cyb-archeology.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 1.25 ETH (197.25 USD @ $157.8/ETH) attached to it as part of the https://github.com/cybercongress fund.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $109,584.86 more funded OSS Work available on the Gitcoin Issue Explorer

from cyb-archeology.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work has been started.

These users each claimed they can complete the work by 1 week, 6 days from now.
Please review their action plans below:

1) mul53 has been approved to start work.

Hi there, really interested in solving this problem

Learn more on the Gitcoin Issue Details page.

from cyb-archeology.

@PumpkingWok hey! By no means your application was wrong. Actually I contacted @janus myself a day before this and discussed the issue with him prior to all other applicants.

I will be opening and funding more issues as soon as this one is solved. Please bare with us. Thanks!

from cyb-archeology.

Issue Status: 1. Open 2. Cancelled

The funding of 0.3 ETH (40.61 USD @ $135.38/ETH) attached to this issue has been cancelled by the bounty submitter

• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $95,671.58 more funded OSS Work available on the Gitcoin Issue Explorer

from cyb-archeology.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 1.25 ETH (169.23 USD @ $135.38/ETH) has been submitted by:

1. @mul53

@serejandmyself please take a look at the submitted work:

• PR by @mul53

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $95,671.18 more funded OSS Work available on the Gitcoin Issue Explorer

from cyb-archeology.

It is like a Far West, eh eh eh !!!

from cyb-archeology.

Looks like it works for me :-)

from cyb-archeology.

Looks like it works for me :-)

It should work ... I have done detailed analysis of the back end javascript and go .. they all produced same result. ... I created codes for them too. So, I told the funder this early morning that the issue is front end .. the mnemonic was a bit twisted. ...

from cyb-archeology.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

The funding of 1.25 ETH (182.67 USD @ $146.14/ETH) attached to this issue has been approved & issued to @mul53.

• Learn more on the Gitcoin Issue Details page
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $98,798.81 more funded OSS Work available on the Gitcoin Issue Explorer

from cyb-archeology.