-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Add example on how to use a custom network #383
Comments
Another useful note would be what fields are required for which parts of the library? For example, to just encode/decode from WIF, only wif is necessary. There do not seem to exist BIP32 prefixes for Namecoin (although I have generated some that generate a prefix of n, if interested... Is this the right thing to do? Or just use bitcoin's?), but they can be simply omitted if you are not using HDNode. It would be nice to know when defining custom networks what is required for my feature set. |
@ricmoo regarding BIP32 prefixes for different coins, I wouldn't recommend doing so as it's pretty redundant (assuming you follow BIP44). See https://github.com/bitcoin/bips/blob/master/bip-0043.mediawiki#node-serialization for more detail. i.e. using |
Oh! That is PERFECT. I have been looking for that info documented somewhere. I noticed a few random alt-coins used their own prefixes. Thanks. :) |
As of bitcoin: {
messagePrefix: '\x18Bitcoin Signed Message:\n',
bip32: {
public: 0x0488b21e,
private: 0x0488ade4
},
pubKeyHash: 0x00,
scriptHash: 0x05,
wif: 0x80,
dustThreshold: 546
}, |
@jprichardson (and others) for what its worth, you should still specify the |
Probably just need to outline something like the following:
The above is
1.5.x
compatible, for2.0.0
see here.The text was updated successfully, but these errors were encountered: