Cannot claim interest for cps in BM 3.1.3 or send cps to another alias - Witness signature not found - code 16 #393
Comments
|
are you using bmd here? can you try via CLI or qt? |
|
Tried both BMD 3.1.3 and qt 3.1.4.
Here is the latest tries from qt as of today:
16:47:33
[cmd-request]
assetallocationcollectinterest 777845ced7b6022b chanakya4 chanakya15
16:47:33
[cmd-error]
SYSCOIN_ALIAS_CONSENSUS_ERROR: ERRCODE: 5003 - Witness signature not found (code 16) (code -1)
16:47:48
[cmd-request]
assetallocationcollectinterest 777845ced7b6022b chanakya15 chanakya15
16:47:48
[cmd-error]
SYSCOIN_RPC_ERROR ERRCODE: 9000 - Witness to this transaction must be different than the funding alias (code -1)
16:48:12
[cmd-request]
assetallocationcollectinterest 777845ced7b6022b bigpoppa chanakya15
16:48:12
[cmd-error]
SYSCOIN_ASSET_ALLOCATION_RPC_ERROR: ERRCODE: 1506 - Could not find a asset allocation with this key (code -1)
16:48:29
[cmd-request]
assetallocationcollectinterest 777845ced7b6022b chanakya17 chanakya15
16:48:29
[cmd-error]
SYSCOIN_ASSET_ALLOCATION_RPC_ERROR: ERRCODE: 1506 - Could not find a asset allocation with this key (code -1)
16:48:44
[cmd-request]
assetallocationcollectinterest 777845ced7b6022b chanakya3 chanakya15
16:48:44
[cmd-error]
SYSCOIN_ALIAS_CONSENSUS_ERROR: ERRCODE: 5003 - Witness signature not found (code 16) (code -1)
16:48:53
[cmd-request]
assetallocationcollectinterest 777845ced7b6022b chanakya6 chanakya15
16:48:53
[cmd-error]
SYSCOIN_ALIAS_CONSENSUS_ERROR: ERRCODE: 5003 - Witness signature not found (code 16) (code -1)
Syscoin.conf does not have reindex =1 row.
If I try to use this alias(chanakya15) as witness for another alias(chanakya16) it lets me claim interest
16:46:32
[cmd-request]
assetallocationcollectinterest 777845ced7b6022b chanakya15 chanakya16
16:46:33
[cmd-reply]
[
"0074000002368ec6a79d2d182e1c9795fb925c09a48c20883eaff45131c757a1a79eb91b83070000007c515914964700ec046d2c723a58d9987f849c895f6e21f588acffffffff8e22d066ca3b98e9bb9aa2bbb78e78fb65bc9d75386973e6e04209884b1bdafa070000004651520a6368616e616b796131351062376230383261373932633030393239000a6368616e616b796131306d6d6d76a914e0a10349af0884b5ff7901fde07eb1eed1adea0088acffffffff036a1d0000000000005e565240623530356530643038313036366463356536306163653537306562333133666164346463356336613830383835376434656361663466633831656234646435316d7576a914e0a10349af0884b5ff7901fde07eb1eed1adea0088ac00000000000000009b6a4c5710373737383435636564376236303232620a6368616e616b796131358e22d066ca3b98e9bb9aa2bbb78e78fb65bc9d75386973e6e04209884b1bdafa88e36688e366000000b76389425f05000000000000000000803e00406235303565306430383130363664633565363061636535373065623331336661643464633563366138303838353764346563616634666338316562346464353130b10000000000001976a914e0a10349af0884b5ff7901fde07eb1eed1adea0088ac00000000"
]
Thanks for looking!
From: sidhujag [mailto:[email protected]]
Sent: Friday, October 26, 2018 5:42 PM
To: syscoin/blockmarket-desktop-public <[email protected]>
Cc: Author <[email protected]>
Subject: Re: [syscoin/blockmarket-desktop-public] Cannot claim interest for cps in BM 3.1.3 or send cps to another alias - Witness signature not found - code 16 (#393)
are you using bmd here? can you try via CLI or qt?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#393 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AneyFA91En23wshYx_v0GsCRwHrc8rmwks5uo4-fgaJpZM4X1xWU>.
|
|
try leaving last arg as "" i dont know why it requires a witness.. it should work without witness.. witness is more for KYC/AML and other things |
|
Same error:
20:25:36
[cmd-request]
assetallocationcollectinterest 777845ced7b6022b chanakya15 ""
20:25:36
[cmd-error]
SYSCOIN_ALIAS_CONSENSUS_ERROR: ERRCODE: 5003 - Witness signature not found (code 16) (code -1)
20:25:57
[cmd-request]
assetallocationcollectinterest 777845ced7b6022b chanakya15 ''
20:25:58
[cmd-error]
SYSCOIN_ALIAS_CONSENSUS_ERROR: ERRCODE: 5003 - Witness signature not found (code 16) (code -1)
20:26:06
[cmd-request]
assetallocationcollectinterest 777845ced7b6022b chanakya15
20:26:06
[cmd-error]
assetallocationcollectinterest [asset] [owner] [witness]
Collect interest on this asset allocation if an interest rate is set on this asset.
<asset> Asset guid.
<owner> Alias or address which owns this asset allocation.
<witness> Witness alias name that will sign for web-of-trust notarization of this transaction. Only applicable asset allocation is owned by an alias.
Requires wallet passphrase to be set with walletpassphrase call. (code -1)
Even if I can claim interest somehow this error doesn’t let me move it to coinpayments or any other alias.
From: sidhujag [mailto:[email protected]]
Sent: Sunday, October 28, 2018 6:37 PM
To: syscoin/blockmarket-desktop-public <[email protected]>
Cc: Rahul Paneri <[email protected]>; Author <[email protected]>
Subject: Re: [syscoin/blockmarket-desktop-public] Cannot claim interest for cps in BM 3.1.3 or send cps to another alias - Witness signature not found - code 16 (#393)
try leaving last arg as "" i dont know why it requires a witness.. it should work without witness.. witness is more for KYC/AML and other things
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#393 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AneyFIPclwyRur-u6pcQx4KmqeyXEMNyks5upj-1gaJpZM4X1xWU>.
|
|
ok let me try this tomorrow |
|
@testingsys - Bear with me, you mentioned: Have you tried entering: ? i.e. using yourself as the witness for collection of interest. We did see this error quite a while back and it resulted from someone using one of their own aliases as the witness for the asset previously in the first place. @sidhujag IIRC if the asset was created using a witness, I remember that we experienced issues if the asset interest claim was attempted without the same witness verifying the claim. Not sure if this is related to that one (as you say, asset interest collection shouldn't require a witness...but I remember the team encountered this issue a little while back for similar reasons). |
|
Yes, tried it and getting this error:
16:47:48
[cmd-request]
assetallocationcollectinterest 777845ced7b6022b chanakya15 chanakya15
16:47:48
[cmd-error]
SYSCOIN_RPC_ERROR ERRCODE: 9000 - Witness to this transaction must be different than the funding alias (code -1)
From: jnessbcf [mailto:[email protected]]
Sent: Sunday, October 28, 2018 10:16 PM
To: syscoin/blockmarket-desktop-public <[email protected]>
Cc: Rahul Paneri <[email protected]>; Author <[email protected]>
Subject: Re: [syscoin/blockmarket-desktop-public] Cannot claim interest for cps in BM 3.1.3 or send cps to another alias - Witness signature not found - code 16 (#393)
Bear with me, you mentioned:
"The alias is chanakya15. I had used this alias as a witness for all my other aliases and it worked fine"
Have you tried entering:
assetallocationcollectinterest 777845ced7b6022b chanakya15 chanakya15
? i.e. using yourself as the witness for collection of interest. We did see this error quite a while back and it resulted from someone using one of their own aliases as the witness for the asset previously in the first place.
@sidhujag<https://github.com/sidhujag> IIRC if the asset was created using a witness, I remember that we experienced issues if the asset interest claim was attempted without the same witness verifying the claim. Not sure if this is related to that one (as you say, asset interest collection shouldn't require a witness...but I remember the team encountered this issue a little while back for similar reasons).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#393 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AneyFHwdwyl9W13B1xM0fhU7NhYkv6TYks5upnL5gaJpZM4X1xWU>.
|
|
hard to read pls clean up your comments.. i will take a look myself |
|
ok.. cleaned up a bit. Here is the summary- So far I have tried: assetallocationcollectinterest 777845ced7b6022b chanakya15 chanakya15 assetallocationcollectinterest 777845ced7b6022b chanakya15 '' assetallocationcollectinterest 777845ced7b6022b chanakya15 "" assetallocationcollectinterest 777845ced7b6022b "" chanakya15 assetallocationcollectinterest 777845ced7b6022b '' chanakya15 My syntax that is working while claiming interest is:
SYSCOIN_ALIAS_CONSENSUS_ERROR: ERRCODE: 5003 - Witness signature not found (code 16) (code -1) |
|
Jags-MacBook-Pro:src jsidhu$ ./syscoin-cli assetallocationcollectinterest 777845ced7b6022b chanakya15 '' |
|
qt also works 10:17:02 | | assetallocationcollectinterest 777845ced7b6022b chanakya15 '' |
|
QT: |
|
ok the issue is on master and its fixed on development branches. |
|
what compile should I use? or wait for the next release? |
|
for bmd pls try next release coming shortly in 3.2, you can compile dev-3.x-prep-3.2.0 though if you want qt or cli to do it |
|
Will wait for the next release then. 5k cps waiting for you once I am able to transfer :) Thanks for your time! |
|
I am still getting the issue on BM 2.0. How do I compile dev-3.x-prep-3.2.0 |
I have a pending cps - claim interest and transfer to coinpayments issue. I have discussed it earlier with locutus and jag, but I put it on hold before I could try to claim interest from blockmarket. Today i have uninstalled BM and QT, deleted all files from the appdata folder(except wallet,mnconf and sysconf), installed bm3.1.3 and right now I am reindexing BM. I have tried reindex several times before, but this is the first time I am doing it after cleanup and reinstall. The issue is - I keep getting this error whenever I claim interest or try to transfer CPS to coinpaments. The alias is chanakya15. I had used this alias as a witness for all my other aliases and it worked fine. And I was able to claim interest on chanakya15 in qt, once earlier with hit and trial with several aliases.This was before 3.1.3. Thanks in advance. Here is the error
5000 cps bounty for any dev who can help me fix this before the next interest cycle. Interest has been claimed once through qt before 3.3. Another interest claim is pending.
The text was updated successfully, but these errors were encountered: