-
Notifications
You must be signed in to change notification settings - Fork 26
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
A nightmare to get the examples running. Release tag matrix from hell [BUG] #102
Comments
Hi @golangdaddy, thanks for the general feedback. Can you please provide more details regarding which package module names do not match the file structure, the examples you're having issues with, and the "release tag matrix from hell"? |
As a user I want to look at the repo and see the latest API/examples, and the whole thing be self-referential and intuitive, not having to follow examples that don't just work without some go mod wizardry with various releases. Even following the examples and fixing the deps, I don't have a working example, so its not a very convenient package. I'm trying to build an SDK over this, so have loads of questions, but as not-a-complete-noob I still have found this one of the most frustrating packages I have come across, happy to lend a hand. |
I would be grateful to know if there is an interface between bip32.ExtendedKey and bec.PrivateKey, I'm building a wallet implementation to learn, which can hopefully have both working in the same manner. |
The above code is what I have managed to glean from the various releases, I'm not confident that I have all the steps covered, as the examples are limited. Any help appreciated, then I can move on and make contributions "unexpected response code 500: 16: mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation)" |
Also the bec.PrivateKey when made into a bitcoin address with the go-bt repo generates a different address than the official instructions on the bitcoin sv website which I translated to this code:
WIF to address: This address has funds on it: 1AdZTNmwE2F5pduveoxNqYhizitnCV5GMP, was hoping this repo would generate the same address from the same WIF. An explanation for this would be useful to include in the readme. |
There are 3 conflicting examples in this repo for the same transaction.
Package module names don't match the filestructure... unintuitive and messy.
Generally needs harmonising with the readme so its enjoyable to use.
The text was updated successfully, but these errors were encountered: