1
General Support - Solved / Re: Staking on Bech32 (bc1) BTC address
« on: March 12, 2021, 01:47:30 AM »
Bumping for exposure
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Hi,
If I run:
# ./biblepay-cli dwsquote 1
{
"Total DWS Quantity": 2060,
"Metrics": "v1.3",
"Total Gross Burns Today": 0,
"Total Burns Today": 0,
"Total Burns in Report": 0,
"30 day DWU": "27.5346",
"90 day DWU": "31.7171",
"180 day DWU": "37.9908",
"365 day DWU": "50.8868"
}
The list with coins I put on stake last year is missing. Are my coins lost?
Well now I've got a new problem. I did the exec bankroll last night and gave it 24 hours. For some reason trying to use easybbpstake didn't work because it found a UTXO of 0.001 more than what I set them for. It was supposed to be a whole number.
Never mind, I think I found my problem. Gotta set up spendable UTXOs before sending a stake I suppose. Question now is, how many blocks do I have to wait to send a stake?
07:39:40

getpin bc1qnx********************************
07:39:40

Address must be 34 characters long. (code -1)
************************************************************************
THANK YOU ALL FOR TESTING BIBLEPAY - EVOLUTION
************************************************************************
Let us pray this version is the most stable and beneficial version for our Orphans and God's Kingdom.
Testing is not completely over, but I wanted to send a warm thank you to everyone who contributed in any way in this TestNet thread!
God Bless you All!
Yeah, the payments will start deterministically based on this new algo, and continue until your node is PosE banned. PosE happens if your node is Off for a certain amount of time (and gets voted down), or if your node isnt participating in the new LLMQs (long living masternode quorums).
As far as the node itself, it cant find its own proreg tx on the chain.
Most likely because the masternodeblsprivkey is missing.
Please copy the key from the deterministic.conf to the node and reboot it and see?
10:07:01

masternode status
10:07:01

{
"outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
"service": "84.29.XXX.XXX:40001",
"state": "WAITING_FOR_PROTX",
"status": "Waiting for ProTx to appear on-chain"
}