auto sending tx didnt work again  same. same here. i found it 5 blocks prior payment block  |
|
|
|
Nice.... What about to mention Dashpay? And @MIP, great work on mobile wallet... Thanks |
|
|
|
I've upgraded my sanctuaries to the latest wallet version (1.4.8.4.) and cleaned them as per Togo's guide. Everything seems to be working fine, but I can't seem to vote. Voting failed! Failed to vote 0 time(s). (Check that sanctuaries are DIP3? Also you must wait 3 minutes in-between re-votes due to network rules.) They are in the DIP3 list and I've been getting rewards consistently. Both controller wallet and sanctuary wallets are on the same chain, and they are not on a fork as far as I can tell... Can you please post the voting command including the id you are using, as I voted manually for Togos proposal and it worked but I did it from the rpc. I tried to vote using the GUI. I can't remember the command to pull all the Proposal ID's, and I don't know if I can copy them from the GUI proposal tab  So I can't try it from the rpc for now. How can I find a list of all the current Proposal ID's that I can copy/paste so I can try it from the rpc? There used to be an overview of all the proposals on pool.biblepay.org right? Ok yes cause I would like to try to reproduce with one that actually throws the gov exception error, so one way, is to type: gobject list all proposals Could you try voting on the woocommerce one? 98e09d657fb771f1559ab046af76d295ebde16f563d35ff9bc95ff738ae725f7 gobject vote-many objid funding yes And let me know if successful and also, then try voting on the one you tried earlier and paste the vote string so I can reproduce? Note that we have not passed the mandatory height yet, but thats another topic (partially related though). Hi... I'm on the same. I tried to vote only in GUI, so I've tried it again with command and here is result: Error: Please enter the wallet passphrase with walletpassphrase first. (code -13) After unlocking wallet it passed succesfully "Voted successfully 1 time(s) and failed 0 time(s)." With unlocked wallet I was able to vote also in GUI... so it looks that the wallet must be unlocked for voting... I didn't know about it |
|
|
|
For those of you who have CPIDs, type this:
exec join wcg
exec associate username wcg_verification_code true
For researchers in PODC:
After all this is successful, you can send a GSC transmission (this contains your PODC daily stake), but you only have to do this once - today - just to test it:
sendgscc wcg
If you leave the wallet on, it will automatically send the WCG stake once per day (at the height shown in 'exec rac').
Nice, it works like a charm I'm in leaderboard now. And really good work on that dashpay... Make it usable also outside USA and it'll be better  Bless you all on Christmas and new year. |
|
|
|
But anyway, having an external miner and pool is amazing in two weeks!
Totally agree with Sunk. Thank you Rob for this and I'm really excited about new future features. PODC (BTW I'm for WCG too) and external miner with NOMP pool could be interesting for newcomers. |
|
|
|
I added two new reports to pool.biblepay.org today: Rob, thank you for that share payment, but to this NOMP stats. Why it's needed to join other site to view stats from NOMP pool. Almost everyone from this conversation is now registered on pool.biblepay.org, but you're expecting new miner to join BBP every day. How they'll found that exists another site where are other stats related to their miners? I think that it'll be good to have this stats on NOMP pool. Or this state is only temporary? |
|
|
|
All blocks solved up to this point were paid out of pool.biblepay.org, also (IE Nomp sent out what it knew about, but pool.biblepay also paid them).
The way the payments are *supposed* to work, Nomp writes the blockhashes down in the database, and wait for them to mature. After 120 blocks, it pays the recipients within 30 mins. We have yet to see any sanity in the process, but once I see a few come in on QT Ill start tracking these babies.
Rob, I'm on NOMP pool almost from beggining, but I did'nt received any payment yet. My worker was B4z5SQtK9hMFkDdAzpMuJXNcPyFhFBPPc1. I started as funded, with pool.biblepay worker, but after ABN shut down I mine standalone. I put to the pool only few VPS, but It would be very bad luck to not have any share in solved blocks. It would be good to see miner statistics (history), lik it's on other pools. I understand that this is beta and maybe this is the future future, but now I'm not able to see my results. So I mine on pool for few days without any payment and I don't know why  With actual diff it's not possible to mine solo for me, so I'm moving to pool.biblepay for now |
|
|
|
** BiblePay - New NOMP Pool - Opening in BETA mode for testing **
I am proud to announce our new NOMP pool is now opening in Beta mode.
I want to create miner "harder" way, but it's not possible. When I put BBP receiving address as miner name it give me this result: Error while Adding Miner
Miner WorkerName must not be greater than 19 characters long. Record Not Saved. Miner Name updated to 19 length on page. (Error 60002) |
|
|
|
New type of error after hitted block on my WIN 1003 miner: Erroring out
[2019-10-13 23:31:59] json_rpc_call failed, retry after 30 seconds
Dying due to unable to convert to bin [2019-10-13 23:32:30] JSON invalid target It stops working, but didn't quit program. This message is rolling over and over again. Restart of miner didn't help. Only reboot of computer (both WIN and Linux) helps. On new start of a miner on linux it gives me this: *** Error in `/usr/local/bin/bbpminer_linux': malloc(): memory corruption (fast): 0x00007f662400ecc0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f6635a0a7e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x82651)[0x7f6635a15651]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7f6635a17184]
/lib/x86_64-linux-gnu/libc.so.6(__strdup+0x1a)[0x7f6635a1e48a]
/lib/x86_64-linux-gnu/libc.so.6(+0xbdd0b)[0x7f6635a50d0b]
/usr/local/bin/bbpminer_linux(+0x458c3)[0x55c0bc5418c3]
/usr/local/bin/bbpminer_linux(+0x41a0e)[0x55c0bc53da0e]
/usr/local/bin/bbpminer_linux(+0x44e2b)[0x55c0bc540e2b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f6635d646ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f6635a9a41d]
======= Memory map: ========
55c0bc4fc000-55c0bcdbf000 r-xp 00000000 fc:00 4331 /usr/local/bin/bbpminer_linux
55c0bcfbe000-55c0bcfe0000 r--p 008c2000 fc:00 4331 /usr/local/bin/bbpminer_linux
55c0bcfe0000-55c0bcfef000 rw-p 008e4000 fc:00 4331 /usr/local/bin/bbpminer_linux
55c0bcfef000-55c0bd032000 rw-p 00000000 00:00 0
55c0bd2f9000-55c0bd31a000 rw-p 00000000 00:00 0 [heap]
7f6624000000-7f662405c000 rw-p 00000000 00:00 0
7f662405c000-7f6628000000 ---p 00000000 00:00 0
7f6628000000-7f6628021000 rw-p 00000000 00:00 0
7f6628021000-7f662c000000 ---p 00000000 00:00 0
7f662c000000-7f662c021000 rw-p 00000000 00:00 0
7f662c021000-7f6630000000 ---p 00000000 00:00 0
7f6630773000-7f6630789000 r-xp 00000000 fc:00 392981 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f6630789000-7f6630988000 ---p 00016000 fc:00 392981 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f6630988000-7f6630989000 rw-p 00015000 fc:00 392981 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f6630989000-7f663098a000 ---p 00000000 00:00 0
7f663098a000-7f663118a000 rw-p 00000000 00:00 0
7f663118a000-7f663118b000 ---p 00000000 00:00 0
7f663118b000-7f663198b000 rw-p 00000000 00:00 0
7f663198b000-7f663198c000 ---p 00000000 00:00 0
7f663198c000-7f663218c000 rw-p 00000000 00:00 0
7f663218c000-7f663218d000 ---p 00000000 00:00 0
7f663218d000-7f663298d000 rw-p 00000000 00:00 0
7f663298d000-7f663298e000 ---p 00000000 00:00 0
7f663298e000-7f663318e000 rw-p 00000000 00:00 0
7f663318e000-7f663318f000 ---p 00000000 00:00 0
7f663318f000-7f663398f000 rw-p 00000000 00:00 0
7f663398f000-7f6633990000 ---p 00000000 00:00 0
7f6633990000-7f6634190000 rw-p 00000000 00:00 0
7f6634190000-7f6634191000 ---p 00000000 00:00 0
7f6634191000-7f6634991000 rw-p 00000000 00:00 0
7f6634991000-7f6634992000 ---p 00000000 00:00 0
7f6634992000-7f6635192000 rw-p 00000000 00:00 0
7f6635192000-7f6635193000 ---p 00000000 00:00 0
7f6635193000-7f6635993000 rw-p 00000000 00:00 0
7f6635993000-7f6635b53000 r-xp 00000000 fc:00 396529 /lib/x86_64-linux-gnu/libc-2.23.so
7f6635b53000-7f6635d53000 ---p 001c0000 fc:00 396529 /lib/x86_64-linux-gnu/libc-2.23.so
7f6635d53000-7f6635d57000 r--p 001c0000 fc:00 396529 /lib/x86_64-linux-gnu/libc-2.23.so
7f6635d57000-7f6635d59000 rw-p 001c4000 fc:00 396529 /lib/x86_64-linux-gnu/libc-2.23.so
7f6635d59000-7f6635d5d000 rw-p 00000000 00:00 0
7f6635d5d000-7f6635d75000 r-xp 00000000 fc:00 396516 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f6635d75000-7f6635f74000 ---p 00018000 fc:00 396516 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f6635f74000-7f6635f75000 r--p 00017000 fc:00 396516 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f6635f75000-7f6635f76000 rw-p 00018000 fc:00 396516 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f6635f76000-7f6635f7a000 rw-p 00000000 00:00 0
7f6635f7a000-7f6635f7d000 r-xp 00000000 fc:00 396514 /lib/x86_64-linux-gnu/libdl-2.23.so
7f6635f7d000-7f663617c000 ---p 00003000 fc:00 396514 /lib/x86_64-linux-gnu/libdl-2.23.so
7f663617c000-7f663617d000 r--p 00002000 fc:00 396514 /lib/x86_64-linux-gnu/libdl-2.23.so
7f663617d000-7f663617e000 rw-p 00003000 fc:00 396514 /lib/x86_64-linux-gnu/libdl-2.23.so
7f663617e000-7f6636197000 r-xp 00000000 fc:00 441287 /lib/x86_64-linux-gnu/libz.so.1.2.8
7f6636197000-7f6636396000 ---p 00019000 fc:00 441287 /lib/x86_64-linux-gnu/libz.so.1.2.8
7f6636396000-7f6636397000 r--p 00018000 fc:00 441287 /lib/x86_64-linux-gnu/libz.so.1.2.8
7f6636397000-7f6636398000 rw-p 00019000 fc:00 441287 /lib/x86_64-linux-gnu/libz.so.1.2.8
7f6636398000-7f66363be000 r-xp 00000000 fc:00 396515 /lib/x86_64-linux-gnu/ld-2.23.so
7f66365b1000-7f66365b6000 rw-p 00000000 00:00 0
7f66365bc000-7f66365bd000 rw-p 00000000 00:00 0
7f66365bd000-7f66365be000 r--p 00025000 fc:00 396515 /lib/x86_64-linux-gnu/ld-2.23.so
7f66365be000-7f66365bf000 rw-p 00026000 fc:00 396515 /lib/x86_64-linux-gnu/ld-2.23.so
7f66365bf000-7f66365c0000 rw-p 00000000 00:00 0
7ffd7e97d000-7ffd7e99e000 rw-p 00000000 00:00 0 [stack]
7ffd7e9c4000-7ffd7e9c7000 r--p 00000000 00:00 0 [vvar]
7ffd7e9c7000-7ffd7e9c9000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
|
|
|
|
1003 crash with -D with this result: The instruction at Ox00007FF878D0D62C referenced memory F at OxFFFFFFFFFFFFFFFF. The memory could not be read. BTW coinabase address is not working for me. It still came to different address. And my experience is, that it looks, that after crash, miner is not able to hit block, till I restart BBP wallet. Run bbpminer is not enough. I don't know if It's true or it's coincidence. |
|
|
|
Should we delete the repo for it, or fix the problem?
Since its unreliable, should we stop developing new things?
No, definitely not. It looks very optimistic and fantastic Let's try to develop it Every new thing need to improve and I know that you'll make it I'll keep it running and try to find those "stop" moments. |
|
|
|
IPFS Decentralized Database https://blog.textile.io/threads-v0-2-community-update/As many people in the community know, we've been working hard on the next big release of Threads, our decentralized database for IPFS. With this upcoming release, we aim to address many requests from you, the developers. Topics we've been exploring include access control, web 2.0 integrations, flexible CRDT support, and more. --- getting 80+ khash on my i5 3.2Ghz 4c/4t the measurement is hard to compare with getmininginfo... but I would say 1.5x to 2x faster than before. Let me know if you can mine solid for 24 hours. I noticed my miner exited on windows last night after 60 minutes. Hi, I've tried that miner too... My experiences: On my laptop Win 10, 64bit, i7 2,8GHz, 4c/8t it is maybe 20% better (around 100kHs) that BBP QT. On my linux VPS it's around 50+% better. But like you said. In one mooment all of my miners stops working. It was on same time (Win and Linux). It was not after 60 minutes. It looks like some "signal" from network which cause this. So, it's interresting, but it looks, that it's not reliable for now |
|
|
|
But as far as hitting blocks, the pool is still hitting 33%. I havent seen a big change recently.
(So these 3 CPKs are solo mining 25% of the blocks I see. I wonder how many machines are being used; I don't think we can tell.)
Ok, I accept that. But I don't have as much luck as you (pool) I hit 90% less blocks. It was after 1146 update (maybe it's coincidence). But I don't remember these 1132 miners before. I'm almost sure, that those miners (except BHVaitQvSJpWqzLJg9N2owCq1W893KQvYP) are new, not "not upgraded". Maybe it is their own version. But yes, they must have enough coins to mine, so from this point of view it looks that's OK. |
|
|
|
Hi Rob, please can you take a look o PoBH mining? Maybe two days ago my miners stoped hiiting a blocks. Today I found, that it looks that there is "some problem" "Version": "Popularity,Percent %",
"1432": "53; 25.85%",
"1445": "124; 60.48%",
"1446": "28; 13.66%" I tlooks that there are miners with wallet version 1432, but mandatory was 1145.... When I took a look to last 500 bloks it looks that first 3 miners are 1432... cpk number of blocks
B96CBZ3ZEAXYp8v8fHD4U4wL8B9PYHSNqf 43
BHVaitQvSJpWqzLJg9N2owCq1W893KQvYP 42
B5Us6y2DSVF9U4w4R4CpBvJfcN1ZF236N1 41 It is OK? Thanks |
|
|
|
And when you sort Announcements (Altcoins) by # of replies we are on the bottom of the first page |
|
|
|
|
Hi,
now I'm using all of my coins only for mining.
Today I solved 9 blocks. I'm using 1436 version on my VPS and 1437b on WIN. Yes, it is laggy, but it works. It looks that I need around 2 hours to reach 256k weight again, I hit the block, It spends all of my coins for ABN and then it goes round and round again. I have not used exec bankroll, but maybe I ll try it. But definitelly it looks, that it is not neccessary, because when you mine all the time, I always hit the block right after all of my coins have coinage 256k and they are spended all.
|
|
|
|
So unfortunately this didn't lead to any new revelations (to improve ABN) yet.
Although this looks strange: ABN Tx Total Bal 1922976.605973, Needed 1926795.382894,
This means the wallet itself, when counting confirmed transactions (coinbases that are confirmed, and all tx's to yourself deeper than 6 confirms) calculates a balance of 1.9229MM, while the ABN coin selector seeks coins of depth 5+ that it would need 1.9267MM to make 256k weight, meaning there is one coin in your wallet (about 4K, probably a reward) that is not quite old enough to be used by ABN.
So by now the miner is probably mining again. Ill try to improve this message.
EDIT: Btw Orbis you can type 'exec getabnweight 256000 1' to see the details of the coins selected to arrive @ 256k.
Ok, I'll take a look on that. It looks, that after a while mining starts again. Maybe after those 4k are old enough. BTW: "total_required 256000.00": 1268252 |
|
|
|
Ok, now I have problem with low ABN again even if my abnweight is more than 256k. Now I found this in log: 2019-06-23 19:49:47 keypool return 2344
2019-06-23 19:49:47 keypool return 2345
2019-06-23 19:49:47 keypool reserve 2344
2019-06-23 19:49:47
ABN Tx Total Bal 1922976.605973, Needed 1926795.382894, ABNWeight 492864.375324 keypool reserve 2345
2019-06-23 19:49:47
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.keypool return 2346
2019-06-23 19:49:47 antibotnetsignature failed on tx f4ced749f1c1eaec7f9c79dd2dd2ffdb20a1604c902f7ce47b7d9926049a5f1c with purported coin-age of 0.000000
2019-06-23 19:49:47 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-23 19:49:47
ABN Tx Total Bal 1922976.605973, Needed 1926795.382894, ABNWeight 492864.375324
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.antibotnetsignature failed on tx 52b553fbba0b42c505ab032ebb3d79479b899c15f43de5e7bc10e736082d8efa with purported coin-age of 0.000000
2019-06-23 19:49:47 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-23 19:49:48 keypool reserve 2346
2019-06-23 19:49:48
ABN Tx Total Bal 1922976.605973, Needed 1926795.382894, ABNWeight 492864.375324
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.antibotnetsignature failed on tx 034ad2e99cc07ac2e319c7c28dbcd6e57b6ba3e0982e48dbbdb54c5f72a56347 with purported coin-age of 0.000000
2019-06-23 19:49:48 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
|
|
|
|
|
Show Posts
