Messages

BTW, I can create a sanctuary as well, need 1 000 000 more tBBP:

yTdd2pbWbHTnxjj8iGmRgzHFraQcMDjP2w

This is the hash Im seeing currently guys:

15:36:49

getblockhash 6100


15:36:49

97f052dc466dbfca07b386618aea0c9d70dccd15b974890d929f0420b1c6c60d

I'm on it

We rolled back 24 hours primarily because I found that the first superblock created had a piece of bad business logic for the first amount, so I moved back to before that first superblock.

Your wallet probably has some orphaned debits, just restart with:
-zapwallettxes=1

And they should then be free.

right, -zapwallettxes=1 helped, thanks!

exec prominence shows empty list now for me:

Code Select Expand


biblepay-cli exec prominence
{
}


getblockhash 4109
341d64d1b90f739dd16500834dffea8e6a4cc3bc514a8ebf0f9fd8467c077de1

OK, seems I am back on the correct chain.

How come that I lost most of my tBBP in the meantime ? (over 2 000 000)
I deleted all files except wallet.dat before starting the newest version.

I see many debit transactions like these:

Code Select Expand


{
    "account": "",
    "address": "yPpyP7oXSH4e5jq8kQuCYFdDnDFbX1B7xU",
    "category": "send",
    "amount": -407184.34410700,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 1,
    "fee": -0.00500000,
    "confirmations": 0,
    "instantlock": false,
    "Anti-BotNet-Transaction": true,
    "trusted": false,
    "txid": "a559a4c16f2c1f6a937412620538da1d0cb4f1dd10fddf7d61b432b0c43d500d",
    "walletconflicts": [
    ],
    "time": 1553805526,
    "timereceived": 1553805536,
    "abandoned": false
  },


there are no matching credit transations for those..

Yes sir exactly, let me try to explain and please let me know if I left anything out.

So now we have ABN mining enabled, and each block requires (about 5005 ABN weight according to getmininginfo).  So no block is accepted in testnet except those over 60 minutes old or those that have the weight.  You can see how much weight yours had by doing : getblock 3109.  It shows: abn-weight : 22500.42.   Thats because the coin amount spent * the age = 22500.42.

Now moving on to the actual transaction, our wallet create an "anti-botnet-transaction" by finding the stake-age, creating the transaction and placing it somewhere in the block (the reason we moved to dynamic block transaction positions, is our wallet now supports chainlocks, and ChainLock might put a transaction in vout[1], so BiblePay made it dynamic).  To find out where it is we have a field called abnlocator, you can find the value by doing a 'getrawtransaction txidvout[0] 1' (for the coinbase transaction) and looking at that transactions output fields, for ablocator, and then get the value and it points to "where" your signed stake is.

As far as the monetary value, the stake was for 30953, but note - all abn transactions are sent to self, so you actually received it all back (IE you spent  , received 30953 + the block reward).  (You also keep the tx-fee because the staker is the solver).

We have very high security on this feature also, as evo doesnt ever allow double spends or malleability, we dont allow stakes sourced from stakes, stakes make people lose coin age, we verify the signature, and also, we verify the solver is the one who created it, so in my experience I feel this is a solid feature.

I also love how it will use up the coin-age for a person who has a couple hundred PCs!  That gives more distinct users to biblepay.

We should also thank MIP and give him half of the credit, because although we spoke about this back when we were designing POL, I forgot about it until he reminded me recently.

May I have few questions?

1. You say ABN weight is about 5005.  His stake was 30953. Is it because he did not have a coin with lower value?

2. From this it seems beneficiary to have multiple smaller coins, otherwise all larger ones would be spent on mining. Is exec bankroll working in evolution?

3. iI the ABN weight moving automatically or is it a static setting?

4. you wrote "we dont allow stakes sourced from stakes". Does this mean that if a coin is spent on a stake, it cannot be spent on another stake again, even after it ages out?

Hey guys,

I would like to join the testing party as well. Would somebody send me some tBBP?

yTdd2pbWbHTnxjj8iGmRgzHFraQcMDjP2w

Thx

[marketed]

I tend to agree with West and Talisman. Making BBP easier to mine does not solve the main issue, the lack of investors who would buy and hold BBP as an investment. Yes, miners can eventually turn into investors and become part of the community, but we still need many more non-mining investors.

BBP has the potential to be very attractive for investors, if it was marketed as "By buying BBP, you are supporting charity + helping to find cures for illnesses, while investing at the same time". The main thing that BBP lacks now is PR and marketing.

That being said, the only new Proof-of-something that would make sense to me would be some kind of Proof-of-PR.
E.g. something that would benefit miners for sending unique IPs to https://www.biblepay.org/<ANYTHING>?ref=CPID_OR_BBP_ADDRESS
or some other referral system. I can see how this could be misused, but you may get the idea

Alright good news, even though it requires an upgrade for the users, good news, I debugged the exec podcupdate feature this morning and I did find a bug!  This explains why T-Mike cant send the exact right stake amount and Simons UTXO is 0 and Rastiks is probably the same issue.

So I now confirm you dont need to worry about the source address of the funds, we will still sign the UTXO packet with your CPID no matter which "bucket" it originates from in the wallet, so that will alleviate a huge portion of the hassle with sending a PODC Update (in the next version).  The other biggie I found was the math the wallet was using was slightly off due to rounding, its kind of hard to explain, but the lions share of the problem was, if you were trying to send say 49K of your 50,000 balance, and your tasks consumed say 3.5K bytes, the internal math (in decimal) rounded down to an amount that was not properly split among the vouts ending with too small of a UTXO expenditure, so I had to fix that so the PODC update leg count (internally) would always round up the specific UTXO for that amount per leg, its a little technical but that is now fixed (in the next version). 

This should be checked in ASAP, doing a little unit testing with this.

Great! thanks

You could try reassociating your CPID again

Well, I tried. Waited 6 blocks, and still the same. Stakebalance shows 50093, but exec podcupdate syas Insufficient funds. UTXOWeight & TaskWeight are zero. May there be something wrong with my CPID ? Maybe, because I have some ARM (tablet + phone) connected to it? I have run out of ideas.

Code Select Expand


# biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "fe553a955f0e21d46724858870014cbe",
  "Address": "BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY",
  "CPIDS": "fe553a955f0e21d46724858870014cbe;",
  "CPID-Age (hours)": 422364,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "fe553a955f0e21d46724858870014cbe_ADDRESS": "BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY",
  "fe553a955f0e21d46724858870014cbe_RAC": 6331.92,
  "fe553a955f0e21d46724858870014cbe_TEAM": 15044,
  "fe553a955f0e21d46724858870014cbe_TaskWeight": 0,
  "fe553a955f0e21d46724858870014cbe_UTXOWeight": 0,
  "Total_RAC": 6331.92,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


Code Select Expand


# biblepay-cli exec stakebalance
{
  "Command": "stakebalance",
  "StakeBalance": 50093
}


Code Select Expand


# biblepay-cli exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."
}


The wallet is quite fragmented after i did several attempts and moved the coins back and forth

Code Select Expand


# biblepay-cli listaddressgroupings
[
  [
    [
      "B7Wtksz1hbBWXRY6U9QhdxMn78h9oEcV5B",
      0.00000000
    ],
    [
      "B7vWrPFoLLawsrpC6hewcxJ6ZbjtPXupV8",
      0.00000000
    ],
    [
      "B8RLs7oTsXvM4QXLQrVVHYwipKqaJXmH4W",
      0.00000000
    ],
    [
      "BB3WzCSGdH6ZYAn5o1a7N4XXKTNcYZ8K6C",
      93.99990840
    ],
    [
      "BCAPPX5PosAcqc5Z4codkaTMLnmQJSwhMX",
      0.00076300
    ],
    [
      "BHRvGs45us9mGimkWimv8kwgYgfmDn2iqm",
      994.99995420
    ],
    [
      "BMskLQZcPd8EUA8c5iHCmCiAruPjVXtUe1",
      0.00000000,
      ""
    ],
    [
      "BQNfVQxb75ssRZ5aqas4Wt2rj6AcPxaZkX",
      48993.99879240
    ],
    [
      "BSF8FbMtBKVJ3XiP7fAtrMSU7NfQGQDtmw",
      0.00000000
    ],
    [
      "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
      0.00000000,
      ""
    ]
  ],
  [
    [
      "BMdWb8WHRbgo6x6AEErNi4cvUVuiKqXn1u",
      0.00000000
    ]
  ],
  [
    [
      "BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY",
      11.00000000,
      ""
    ]
  ]
]


You could try reassociating your CPID again

Have just tried that. So far still zero UTXOWeight, but let's wait 6 blocks. But frankly, I do not believe in success.

I have the same issue. Plenty of BBP to stake, but zero UTXOWeight. Sent the BBP to the address from exec getboincinfo, now waiting for 6 confirms to see what happens.

aargh. Still not working for me. I have > 50 000 BBP in the wallet address from exec getboincinfo. Stakabalance confirms that. But my UTXOWeight is still 0, and exec podcupdate says Insufficient funds.

This is the second node I'm trying to make this runing (started from scratch today, since it did not work for me yestarday).

Code Select Expand


# biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "fe553a955f0e21d46724858870014cbe",
  "Address": "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
  "CPIDS": "fe553a955f0e21d46724858870014cbe;",
  "CPID-Age (hours)": 422363,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "fe553a955f0e21d46724858870014cbe_ADDRESS": "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
  "fe553a955f0e21d46724858870014cbe_RAC": 6007.06,
  "fe553a955f0e21d46724858870014cbe_TEAM": 15044,
  "fe553a955f0e21d46724858870014cbe_TaskWeight": 0,
  "fe553a955f0e21d46724858870014cbe_UTXOWeight": 0,
  "Total_RAC": 6007.06,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


# biblepay-cli exec stakebalance
{
  "Command": "stakebalance",
  "StakeBalance": 50099
}

# biblepay-cli listaddressgroupings
[
  [
    [
      "BCAPPX5PosAcqc5Z4codkaTMLnmQJSwhMX",
      0.00076300
    ],
    [
      "BMskLQZcPd8EUA8c5iHCmCiAruPjVXtUe1",
      0.00000000,
      ""
    ],
    [
      "BSF8FbMtBKVJ3XiP7fAtrMSU7NfQGQDtmw",
      0.00000000
    ]
  ],
  [
    [
      "BMdWb8WHRbgo6x6AEErNi4cvUVuiKqXn1u",
      0.00000000
    ]
  ],
  [
    [
      "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
      50099.99900000,
      ""
    ]
  ]
]

Code Select Expand


# biblepay-cli exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."
}



Your stake needs to be in the
"Address" from
exec getboincinfo

I have the same issue. Plenty of BBP to stake, but zero UTXOWeight. Sent the BBP to the address from exec getboincinfo, now waiting for 6 confirms to see what happens.

Did you check to see if the coins were in BPzKKaUa2yXDufhd1YchEZDHY7aSLrvmyC?

They were  not Moved to that address (https://biblepay-explorer.org/address/BPzKKaUa2yXDufhd1YchEZDHY7aSLrvmyC), but  stakebalance is still 0, "PODCUpdate": returns "Unable to create PODC UTXO::Balance too low."

Hi, what's  wrong in my case? > 50000 in my wallet, but with zero TaskWeight and zero UTXOWeight, StakeBalance is 0.

Code Select Expand


# biblepay-cli getblockchaininfo
{
  "chain": "main",
  "blocks": 33446,
  "headers": 33446,
  "bestblockhash": "2ec8d52a70e382beb1bd0c5181f68581534799042e86112db6896a0468a38809",


Code Select Expand


# biblepay-cli getwalletinfo
{
  "walletversion": 61000,
  "balance": 50001.99963080,


Code Select Expand


# biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "fe553a955f0e21d46724858870014cbe",
  "Address": "BPzKKaUa2yXDufhd1YchEZDHY7aSLrvmyC",
  "CPIDS": "fe553a955f0e21d46724858870014cbe;",
  "CPID-Age (hours)": 422349,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "fe553a955f0e21d46724858870014cbe_ADDRESS": "BPzKKaUa2yXDufhd1YchEZDHY7aSLrvmyC",
  "fe553a955f0e21d46724858870014cbe_RAC": 3283.5,
  "fe553a955f0e21d46724858870014cbe_TEAM": 15044,
  "fe553a955f0e21d46724858870014cbe_TaskWeight": 0,
  "fe553a955f0e21d46724858870014cbe_UTXOWeight": 0,
  "Total_RAC": 3283.5,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


Code Select Expand


# biblepay-cli exec stakebalance
{
  "Command": "stakebalance",
  "StakeBalance": 0
}