-
Notifications
You must be signed in to change notification settings - Fork 5
RPC error: -25: Min anchor quorum was not reached! #6
Comments
Don't ask me why, but this is normal behavior. |
Please let your node run for half an hour to get the anchor auth information, and you can use the below API to check if you node received the anchor auth nodes.
|
@AltCoiFish More information can be found in the link below. https://github.com/DeFiCh/ain/wiki/What-is-an-anchor%3F |
Anchor teams creating the auths and confs can be found with getanchorteams.
Auths used in anchor creation require signatures from 66% plus one members of the team to meet quorum.
The latest auth seen in spv_listanchorauths shows that this is not met for the team above. Further info is in the link I posted above. |
Thank you for your replay. My defid Node is running more then 12h and still an emmpty respond:
I understood it like this, this should stay empty until the new Anchor team is created and they create the Anchor Data? Thanks for helping out here. |
As a suggestion , after you did upgrade to version 1.5. did you start your Not sure if its related here. |
Can you share your command line parameters for defid? And upload the log in |
What is the result of spv_syncstatus? |
I start from scratch, new Host and new BTC and DEFI Host, |
So guys, I'm one step closer, I think.
Which is wired, that the Transaction didn't go through, yet, and the potential rewards is 55, where I see in the DEFI Block Explorer at that time 35 DFI. When then Enabling in the config.toml: I recive directly an error:
Find attached my config.toml. (I removed the RPC Part) and the ~/.defi/debug.log |
After restart the DeFi Node had had the same issue again that |
You node log has a lot of error like this, means the anchor syncing have problem, can you restart your node with
|
I did. I stopped Checked the Status with
The debug.log look first (after sync) good, but then I spotted again some errors: But when
Then I run the Script again after around 30min, after the I attached my defi.conf, debug.log and spv.log |
There is a new version of DeFichain released soon that has a few updates for anchors. You could be running into issues related to those updates. After updating you will need to run -spv_resync again. |
After doing nothing on the Node, the Script went through. Nothing Changed
However when checking the the Transaction, all look fine. How can I find the anchor team confirmation? |
You can use spv_listanchorrewardconfirms to see the anchor confirms and spv_listanchorsunrewarded to see unrewarded anchors. Your anchor needs to be seen as active in spv_listanchors by the majority of the anchor confirm team to be confirmed for reward payment. |
Thank, I was able to verify the transaction. Solution for Future reference: First try to start the node with After Sync is complete, wait until Anchor History is build, If that doesn't help, rebuild the entire Blockchain. Thank you all for the support! |
Hi Guys,
Since this morning I run the script as well.
I always received the following output, where I start the Script as follow:
./main.py --config ./config.toml --repeat 30
I see the following Result in the Consol from the Script:
When I check
defi-cli spv_listanchorauths
I got a empty respond.Is my assumption correct that the Script is working fine, but there is nothing to Anchor yet?
I reffering to https://github.com/DeFiCh/ain/wiki/Create-Bitcoin-Anchor where it staters:
"f it empty, then need to wait for 15 blocks to let your node to receive the anchor auths message"
As far as I understood the Script, this Error is not covered in the error handling of the Script?
Or is something wrong with my Setup?
RPC's are running both. Funds also available.
The text was updated successfully, but these errors were encountered: