-
Notifications
You must be signed in to change notification settings - Fork 94
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
Support posv #1815
Support posv #1815
Conversation
Yes, it should address that issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for the PR! I have two change requests :)
used the following settings for POT:
and tried to withdraw some POT to some other address
|
similar with RDD and this settings:
|
I think there is a problem with the transaction serialization @reddink Edit: nevermind, this is what is actually done, I was using the wrong branch to check this. |
@cipig @reddink I think I found the problem, it's related to |
Additionally {
"coin": "RDD",
"name": "reddcoin",
"fname": "Reddcoin",
"isPoS": 0,
"isPoSV": 1,
"rpcport": 45443,
"pubtype": 61,
"p2shtype": 5,
"wiftype": 189,
"decimals": 8,
"txversion": 2,
"txfee": 0,
"dust": 10000,
"segwit": false,
"bech32_hrp": "rdd",
"mm2": 1,
"required_confirmations": 1,
"avg_blocktime": 60,
"protocol": {
"type": "UTXO"
},
"derivation_path": "m/44'/4'",
"trezor_coin": "Reddcoin",
"links": {
"github": "https://github.com/reddcoin-project/reddcoin",
"homepage": "https://reddcoin.com"
}
}
The tx version was also incorrect.. i suspect the same with potcoin (ver 4???) |
Thanks for the fixes, i will try it out. Not sure if it needs txversion set, i guess not... will try that out too :-)
i use 62.171.189.243:50001 |
I think txversion is required. |
ok, will try with txversion set
what is the usual fee (in sats per kbyte)? EDIT: could not find EDIT2: to me it looks like the usual fee should be 100000 sats per kbyte, found things like this in code:
|
For this testing 100000 sats should be fine, this has been used on most electrumx servers |
Bech32 hasn't been enabled on mainnet yet, currently doing testing on testnet however, we can leave it out for the moment |
looks good, i could send a RDD tx: https://live.reddcoin.com/tx/8006e3425a3bbac3c35f28aca4d67c7622b76cf21567221de08868c3328b7963 what about BIP65: https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki ? |
Bip65 is being activated on mainnet with our v4.22 core wallet. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only 2 more minor changes! Please also resolve the merge conflicts!
@cipig should we add |
|
It's good we added support for witnesses in the code, once |
Thanks for the contribution @reddink |
@reddink we seem to be facing issues with sending RDD transactions in the current apps. The error is as previously mentioned in this thread - Can you please check and confirm / tweak the values in https://github.com/KomodoPlatform/coins/blob/master/coins#L9333-L9360 ? |
@smk762 do you have a copy of the raw transaction i can analyse? |
here you go - [
|
Thanks for that, super helpful.. So the error returned by the electrum sever is slightly different, 'tx decode failed'. Taking a look at the structure of that rawtx I will take a look at the logic to see if I can track down the discrepancy. |
@smk762 problem was at ln#780 /mm2src/coins/utxo.rs the line should read have created a seperate pull request |
This PR enables PoSV type transactions from the likes of Reddcoin, Potcoin, et al.
The differentiator over the existing POS implementation is that the n_time is appended to the end of transaction (after locktime) rather than being at the 2nd position in the structure
Additionally, the n_time field is not used in the sign process, but is appended to the transaction after inputs are signed