|
Ok 1.0.0.3 didnt last much longer, but now Im running one in debug mode in gdb and another one in valgrind.
Ill keep debugging until we find the cause of the crash.
|
|
|
|
Youd have to run it in valgrind to get the actual trace info; how many hours at a time did it run with coinbase addr set?
Edit: thats great you mined a block; I assume the reward came to a brand new key.
valgrind is for Linux isn't? Couldn't find a Windows version. Maybe this? http://www.codersnotes.com/sleepy/I am not sure if coinbase-addr sends to the address I specify, but I'll have to keep checking. I also put a coinbase sig text. I think something is getting saved into the blockchain (according to chainz), but not the text I specified. Windows would require a full environment to be setup to debug in so lets avoid that for now. On the coinbase address, I see the issue with that - its preferring the address biblepaycore is sending (as if you started to solo mine) - I can fix that in the next version; but I have a question, when you say you injected a signature to be checked in chainz, what do you mean? --coinbase-addr=ADDR payout address for solo mining --coinbase-sig=TEXT data to insert in the coinbase when possible So, when you specify a --coinbase-addr , you can specify a specific reward address to send to. For my use case, different receiving would tell me which computer is mining rewards. --coinbase-sig=TEXT in the raw output of the block, you will see your custom text included with mined block. This is low priority. It is just a feature supported with minerd for bitcoin back when cpu mining was viable for bitcoin. Ok, now I know which command you used to embed a coinbase sig. Yeah, we will have to take that option out as we dont support custom coinbase signatures (they must be made from the core wallet, due to chainlocks being implemented soon, which requires binary data to be stored and the signature therefore wont be calculated from the external miner). However we do support custom prayers and messages, but again - the external miner wont have the capability to insert a custom prayer or message from the mining side. But we will be able to support the custom payout address, somehow - soon as we get closer to a pool. |
|
|
|
i tried install new wallet on new machine with VOLODAJs wallet.dat
no chance, still no see bbp in wallet
Bottom line is Sun showed that the BBP moved out of that wallet to a new address (when he pasted the BX link). So I want to clarify, what needs done is someone should see the public key it was sent to - see if that key is in the wallet you are trying to recover. You need to recover the wallet.dat that received the BBP. The good news is - no Biblepay can ever dissapear, its always in one place or another - unless : A) Coins are burned B) Coins are mined on a fork So in this case the coins are recoverable, unless the coins were stolen. |
|
|
|
Thanks, couldnt get anything out of the windows side, we would have to add the windows stacktrace. Lets see if this last version running in Debug mode is revealing. |
|
|
|
I was able to compile the new miner on Ubuntu following these instructions: https://github.com/biblepay/cpuminer/blob/master/BuildingBBPMiner.txtRunning it maxed out all my CPUs automatically, 16 threads, about 24 khash/s on each thread, Ryzen 7 1700 = To help slovakia proof the .txt instructions, I would recommend adding these two commands at top for self compiling: git clone https://github.com/biblepay/cpuminer/
cd cpuminer = 1. Have Wallet Installed and Updated v1.4.5.0+ 2. Edit biblepay.conf with needed config options (and comment out pool settings), Restart Wallet 3. Have Wallet unlocked and with aged coins for ABN (AntiBotNet), Keep wallet running 4. Install and Run the bbpminer (it is separate and connects to the wallet through RPC) Reference: https://bitcointalk.org/index.php?topic=2388064.msg52730089#msg52730089Thanks, I added those two lines today, and also a missing line for the dependencies. |
|
|
|
I was able to compile the new miner on Ubuntu following these instructions: https://github.com/biblepay/cpuminer/blob/master/BuildingBBPMiner.txtRunning it maxed out all my CPUs automatically, 16 threads, about 24 khash/s on each thread, Ryzen 7 1700 = To help slovakia proof the .txt instructions, I would recommend adding these two commands at top for self compiling: git clone https://github.com/biblepay/cpuminer/
cd cpuminer = 1. Have Wallet Installed and Updated v1.4.5.0+ 2. Edit biblepay.conf with needed config options (and comment out pool settings), Restart Wallet 3. Have Wallet unlocked and with aged coins for ABN (AntiBotNet), Keep wallet running 4. Install and Run the bbpminer (it is separate and connects to the wallet through RPC) Hey man. I've been on hiatus from this forum several months ago (especially on the technical side) and would really like to pickup from what I left. I've been interested to this coin few months ago but didn't have the time/effort to take plunge into it. Currently, there are a lot of questions that I would like to ask because there seems a lot of changes happened here. - A - First is that am I reading it correctly? I can run a mining software for this coin and it will only use my CPU?
- B - Would it be alright to use it on my laptop? This is a gaming laptop with pretty decent cooling hardware.
Hi Janpri, A) Yes, you can mine on the cpu only. So far to our knowledge in this community no one has used a GPU or asic yet. You can see the mining instructions for cpu on the OP page. Its probably better to get started using those first as that miner is stable. What we are doing now with this external miner is debugging it to see if we can get the plane off the ground. The biblepay client has a built in miner that works in a stable way. B) Yes you can mine on a laptop - we have pool mining or solo. See the Getting started with Evolution guide in the OP post (its a wiki page). Welcome aboard! |
|
|
|
Youd have to run it in valgrind to get the actual trace info; how many hours at a time did it run with coinbase addr set?
Edit: thats great you mined a block; I assume the reward came to a brand new key.
valgrind is for Linux isn't? Couldn't find a Windows version. Maybe this? http://www.codersnotes.com/sleepy/I am not sure if coinbase-addr sends to the address I specify, but I'll have to keep checking. I also put a coinbase sig text. I think something is getting saved into the blockchain (according to chainz), but not the text I specified. Windows would require a full environment to be setup to debug in so lets avoid that for now. On the coinbase address, I see the issue with that - its preferring the address biblepaycore is sending (as if you started to solo mine) - I can fix that in the next version; but I have a question, when you say you injected a signature to be checked in chainz, what do you mean? |
|
|
|
ROB after upgraded, still crashing on my side...... dont know what the others
same case even upgrade to 1.0.0.2. crashing at the same time.... report: Bus error (core dumped)
or
7fbf57dbb000-7fbf57dbc000 rw-p 00000000 00:00 0
7ffe056a5000-7ffe056c6000 rw-p 00000000 00:00 0 [stack]
7ffe0570d000-7ffe05710000 r--p 00000000 00:00 0 [vvar]
7ffe05710000-7ffe05712000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
Aborted
I just checked in 1.0.0.3, lets run it with the "-D" switch at the end of the command line, and see if it reveals the problem. (Or if its fixed now). |
|
|
|
super Rob, last 4 hours im stable too  Ill put more logging in to find out whats happening when it exits. Regarding one-click setups, regardless of the whole environment, once we establish a stable 'secret sauce' we will work on one click setups again. The miner can be launched from biblepaycore - anything is possible. |
|
|
|
ROB after upgraded, still crashing on my side...... dont know what the others
I ran for 4 hours this time (400% longer) and the exit wasn't a crash, are you sure you are "mining"? |
|
|
|
Biblepay CPU Miner
1.0.0.2-Leisure Upgrade
- Fix memory corruption error causing a crash - Handle no work received I cant say 100% the problem is resolved (as the valgrind trace was very vague), but this is the new version Im testing with tonight: https://github.com/biblepay/cpuminer/tree/master/binariesFeel free to upgrade and join me.
|
|
|
|
|
Regarding the new external miner debugging issues, I don't have time to reply to the posts right now as Im due to be at an event, but what I will do is start the miner in debug mode in linux (ubuntu 18) and mine against prod while Im gone, and most likely it will show us the trace info by the time I get back - and with any luck then I will fix the issue ASAP after that.
So dont worry about debugging in windows, most likely we will catch it in linux tonight.
|
|
|
|
miner.exe bad results on my ryzen1700.... tested 10minutes
12-17 khs/thread
classic way is easy and better... MUCH BETTER
I disagree: - The new one is faster and closer to the machine - The new one has stratum - The new one allows us to accomplish more |
|
|
|
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. Could you please run it with the --coinbase-addr= populated? And the "-P" flag and the "--no-longpoll"? So far I havent exited with a coinbase addr populated. Ill see what I can do about debugging it - we might have an exit program in there when it doesnt get work (in contrast to retrying). Btw if you have a reproducible exit, let me know. I was able to mine a block with the external miner: https://chainz.cryptoid.info/bbp/tx.dws?1157341.htm (see version 1.4.5.0) I'll help with -P RE: Crashing Crashtimes: 10:54:57 PM and again at 12:04:24 AM PDT According to microsoft, the exception code is a heap corruption: https://blogs.msdn.microsoft.com/calvin_hsia/2015/01/30/heap-corruption-exception-0xc0000374/Faulting application name: bbpminer-x86.exe, version: 0.0.0.0, time stamp: 0x5da08c5b Faulting module name: ntdll.dll, version: 10.0.17763.802, time stamp: 0x125ac1e8 Exception code: 0xc0000374 Fault offset: 0x00000000000fb049 Faulting process id: 0x1af0 Faulting application start time: 0x01d580c325d339ff Faulting application path: C:\Users\xxx\Downloads\bbpminer-x86.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: bfd34ddb-3275-41ba-ab8a-d9fc19a0ddaf Faulting package full name: Faulting package-relative application ID: Youd have to run it in valgrind to get the actual trace info; how many hours at a time did it run with coinbase addr set? Edit: thats great you mined a block; I assume the reward came to a brand new key. |
|
|
|
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. Could you please run it with the --coinbase-addr= populated? And the "-P" flag and the "--no-longpoll"? So far I havent exited with a coinbase addr populated. Ill see what I can do about debugging it - we might have an exit program in there when it doesnt get work (in contrast to retrying). Btw if you have a reproducible exit, let me know. |
|
|
|
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 Should we delete the repo for it, or fix the problem? Since its unreliable, should we stop developing new things? |
|
|
|
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. 10-4 on the speed. I estimated my windows box at 350KHS with 16 threads last night, while the core was 250KHS (about a 40% increase). EDIT: Going to run this baby with the --coinbase-addr= populated for a while - and see if there is a difference on windows. |
|
|
|
|
BiblePay
1.4.5.0-Leisure Upgrade
- Add getblockforstratum rpc call to help support external cpu miner
(bbpminer.exe)
- Add exec pobh call for dev use (this allows us to test bible hashes
manually)
- Fix instantsend GUI confirmation for signed/accepted IXs
- Add icon for decentralized network
- Increase IX timeout for locks and sigs
- Decrease memory consumption for votes and decrease network utilization
(Remove duplicate votes)
** This is the windows release; MIP will post when the rest of the binaries are ready **
** Now windows users, we can test mining with windows bbp-miner.exe against this windows build **
|
|
|
|
|
Before I forget, here is another side project I think deserves attention.
I believe we can actually quantify the original dash project, xcoin/darkcoin/dash into its emissions, miner count, economy of scale, lost coins, and other factors into a "model". I think it would be extremely interesting if we could model the effect of ASIC mining, emissions, miner liquidations, investors, investor liquidations, buy and hold %, locked coins into a graphed timeline.
That would theoretically allow us to tune the model to the actual results (matching it to 2019).
Then we take this model and re-run it for BBP. Then we gather the information (the pros) that make BBP into a winner.
Although people might argue the inputs would be theoretical, I think if we intelligently estimate the inputs and arrive at where Dash is now, we could gain insight into what could potentially make BBP explode (and know what decisions we made that hinder BBP) - for example if POG/POOM hurt us etc.
It would also be potentially usable as a future expectation for ROI - a graph with no guarantees of future results (entirely speculative) but one that offers a potential what-if our coin follows the model.
|
|
|
|
|
Show Posts
