Show Posts
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.
Yeah, I wanted to do this earlier, but I don't understand this step:
'go to bash, cd /SAN'
So I upgraded all my sancs to ensure Togo is going to come through, at least on my end of the deal, hey Mike, can you try that thing I posted for Sanc testing to ensure your sanc will process Togos CPID?
cat filtered | grep 9313 -A10 -B10
<name>strayapple</name>
<id>1981219</id>
<utxoweight>75</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>
</user>
<user>
<teamid>15044</teamid>
<url>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs</url>
<cpid>93138f032bdd027fa3246b48bb715a77</cpid>
<expavg_time>1520462480.639447</expavg_time>
<expavg_credit>80933.641932</expavg_credit>
<total_credit>1254458.742816</total_credit>
<create_time>1517967718</create_time>
<country>United States</country>
<name>togoshigekata</name>
<id>1981221</id>
<utxoweight>100</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>
Its really OK if the wallet makes it through phase 1 of association and fails (IE changes your boinc URL) as that is just part of the process, but as far as it failing due to cannot sign cpid:
That means the wallet is locked. Try sending some bbp to yourself with 'sendtoaddress address 1' first, then run the exec associate command. Then it should pass.
Yeah, I need to inform everyone on the main thread of the big change, we now use "utxoamount=X" across the board. Ill do that when windows is done building and explain it in that message.
So on your tx, I do see your CPID e94* in my utxoweight list being 100, so that is great.
The reason its 100 is you sent : 106.3K in leg 1 of your UTXO transaction.
Dont worry about debugging it, the last versions squirrely math might have sent an unpredictable amount, the new version should be dead on every time and send change back to you.
exec getboincinfo
{
"Command": "getboincinfo",
"CPID": "e94c1704c75f731f8bfde303f08408ee",
"Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
"CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
"CPID-Age (hours)": 422364,
"NextSuperblockHeight": 33620,
"NextSuperblockBudget": 2660579,
"e94c1704c75f731f8bfde303f08408ee_ADDRESS": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
"e94c1704c75f731f8bfde303f08408ee_RAC": 58863.33,
"e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
"e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
"e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 100,
"Total_RAC": 58863.33,
"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
}
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.
Status: 25 confirmations, broadcast through 7 nodes
Date: 3/8/2018 04:35
Source: PODC-Update
Total debit: -15 762.10882064 Biblepay
Total credit: 15 762.10882064 Biblepay
Transaction fee: -0.00500860 Biblepay
Net amount: -0.00500860 Biblepay
Height: 33524
Difficulty: 0.000000
Time: 03-08-2018 09:49:06
Subsidy: 555.4128
PODC_UPDATE:
Transaction ID: 272c95b9f40a5d3a7d18c2b925301f79dc334845abb80272d04c9258c8a94b8a-000
Yeah, I have the same issue. Im pretty confident we didnt break anyone with that, I took a look at it again.
So Im building windows, but it probably wont be ready til 6 am as its been quite a long day for me
Ok, I should be around for another 40 mins, but just in case, if something goes wrong with this, try to do this:
sendtoaddress your_bbp_address allOfYourBBP
See if sending it all to your primary wallet recv address helps the podcupdate send properly, but only do if this new build does not work as intended
Ok, I went ahead and modified PODC Updates to use Amounts instead of percentages.
So if you want to grab the latest code, we no longer use "-polpercentage". We now use "utxoamount".
The default is now 50K.
Please let us know if this works, and that I did not break everyone.
So you set your wallet like this:
utxoamount=40000
For example, but the default is 50K.
I'll do that. Why set a percentage anyways? What happens if I remove polpercentage?
If you remove it uses 10%. We have it in case you have a 30 Million balance or something, as some people may freak out if it sends out all your money every time it stakes
If you want to test your Sancs health with Togos cpid his cpid is 9313, you can type 'exec dcc', and when its done go to bash, cd /SAN, then
cat filtered | grep 9313 -A10 -B10 and take a look at Togo's <taskweight> and it should be up to 100.
cat filtered | grep 9313 -A10 -B10
<name>strayapple</name>
<id>1981219</id>
<utxoweight>75</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>
</user>
<user>
<teamid>15044</teamid>
<url>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs</url>
<cpid>93138f032bdd027fa3246b48bb715a77</cpid>
<expavg_time>1520462480.639447</expavg_time>
<expavg_credit>80933.641932</expavg_credit>
<total_credit>1254458.742816</total_credit>
<create_time>1517967718</create_time>
<country>United States</country>
<name>togoshigekata</name>
<id>1981221</id>
<utxoweight>100</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>
I think in this case its best to go into coin control, and wait til you have 6+ confirms available for the whole 100K of UTXO's, then set polpercentage=90, and do it again, im guessing when you sent it the last time, at least one of your inputs didnt have 6 depth in the chain (you can see the depth in coin control).
He could probably weld a bridge together or fly a 737 with that much power (in watts), wow.
I hope he doesnt find out about BBP too fast, unless he buys some Sancs from the open market.
I wonder what team he is on.