BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[bible_pay]

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

[1714048320]

1714048320

[1714048320]

1714048320

[bible_pay]

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.

[bible_pay]

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/binaries

Feel free to upgrade and join me.

[slovakia]

ROB after upgraded, still crashing on my side......  dont know what the others

[bible_pay]

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"?

[slovakia]

super Rob, last 4 hours im stable too  


edit:// now crashed and dont know run it

[bible_pay]

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.

[eternalenvoy]

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:

Code:

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

[slovakia]

crashed too

[bible_pay]

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:

Code:

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).

[bible_pay]

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?

[bible_pay]

I was able to compile the new miner on Ubuntu following these instructions:
https://github.com/biblepay/cpuminer/blob/master/BuildingBBPMiner.txt

Running 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:

Code:

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!

[bible_pay]

I was able to compile the new miner on Ubuntu following these instructions:
https://github.com/biblepay/cpuminer/blob/master/BuildingBBPMiner.txt

Running 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:

Code:

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#msg52730089

Thanks, I added those two lines today, and also a missing line for the dependencies.

[bible_pay]

So, few minutes later all miners crashed again.
On linux I wasn't able to catch anything, but I have something from Windows.
In "-P" was nothing special, only that hex part was a lot longer. Here it's pasted: https://pastebin.com/rKTpbvAz
I have 3 events from Event viewer: https://filebin.net/peeykdltqyu9td6v

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.

[bible_pay]

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.

[sunk818]

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.

[sunk818]

again miner for 5-6 users

sunk,orbis,rob and etc......

where is so easy way for miners? nonstop hard to setup


WE WANT TO 1 CLICK SW.MINER like on others coins

BIBLEPAY where is that coins from wallet? i tried install new wallet on new machines and replace friends wallet.dat  ... see on this  I CAN SENT WALLET.DAT to you and check it....

BB5h6ud4znPzFFqb5T6PR9JMidjdDRAwmD

If you have the private key for the above public key, you will have most of the coins.

in tools, debug console:


xx:xx:xx dumpprivkey BB5h6ud4znPzFFqb5T6PR9JMidjdDRAwmD
xx:xx:xx Private key for address BB5h6ud4znPzFFqb5T6PR9JMidjdDRAwmD is not known (code -4)

I don't have the private key so I get this answer. But if you have the private key, wallet will say.

Then once you have this key, copy to safe place (like password manager).

start biblepay brand new with brand new wallet.

then do:

importprivkey privatekey

make sure to keep private key secret.

[bible_pay]

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.

[bible_pay]

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.

[sunk818]

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.

One Windows 10 computer I didn't do all the security updates (it has been off for several months) mined for 12+ hours (on 1.0.0.1 bbpminer version) with no issue.

I want to speculate that crashes seem to occur when a GSC using up all the coinage inputs (ABN starved) or when the contents fo the UTXOs change, the miner gets confused? If ABN is off on testnet, this would be an easy thing to test in TestNet for me.