Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 87. (Read 243376 times)

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



thanks....god bless this coin 

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

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.

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. 

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:

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.

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.

Should we delete the repo for it, or fix the problem?

Since its unreliable, should we stop developing new things?

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

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.

i tried install new wallet on new machine with VOLODAJs wallet.dat


no chance, still no see bbp in wallet

Linux and MacOS binaries ready

mercatox is notrustworthy, its next robot exchange like tokok and south

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.

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.

*** External POBH (Heat/POW) miner being released now for testing in Prod or TestNet ***

Remember you will need to upgrade biblepay to 1.4.5.0+ first before you can use this miner (that release will be out shortly).  And, this release will only work in solo mining mode (so please comment out the pool entries).  And, you will need a self-funded abn, and the wallet unlocked for mining (so the internal core can create ABNs when needed).

1)  Repo for the new bbp-miner.exe:
https://github.com/biblepay/cpuminer

2) To build it yourself:
https://github.com/biblepay/cpuminer/blob/master/BuildingBBPMiner.txt

3) Binaries for Windows and for Linux (x86_64):
https://github.com/biblepay/cpuminer/tree/master/binaries

Windows Link:
https://github.com/biblepay/cpuminer/blob/master/binaries/bbpminer-x86.exe

Linux link:
https://github.com/biblepay/cpuminer/blob/master/binaries/bbpminer_linux

For more distros we will need to ask MIP to help us.

USAGE INSTRUCTIONS (SOLO MINING):

./bbpminer -o127.0.0.1:rpc_port_number -uYour_RPC_Username -pYour_RPC_Password --no-longpoll

BiblePay Configuration file (biblepay.conf):
server=1
rpcport=14000 (or your own number)
rpcallowip=127.0.0.1
rpcuser=your_rpc_username
rpcpassword=your_rpc_password


Please post if you have any trouble and we can all try to help.

We got an offer to be listed on Mercatox for 1btc, and although I could see us counteroffering 0.10 btc for the listing, according to these reviews they appear to not honor peoples withdrawals:

https://www.trustpilot.com/review/mercatox.com

(65% say problems withdrawing coins).

So I think we will need to pass.

I'm traveling this week so I'll be a little less available than normal but things are still happening in the morning (development wise).

Let me give a quick update on what changes are coming and updates on a few things:

1) The BiblePay external CPU miner is almost ready for testing (you can test against production or testnet).  I am formulating a strategy for our future, as related to POW/PODC/POG.  From a high level, one thing Im dissapointed about is the lack of increase in new users.  I want to see at least one new user per day.  Ive decided that maybe we were a little too stringent, trying to appeal to Christians only, when really we should appeal to everyone - and expose the everyday people to the gospel of Jesus over time.  Actually this is what Jesus wanted to do anyway - why do you eat with tax collectors and sinners?  Because we are to spread the gospel to those *in need* of it not those who already know the gospel.

In light of that, I think a "more user friendly" strategy for biblepay is to lower the ABN, to something more affordable for one.  The poll was all over the place (and relatively neutral overall).  So lets talk about this in a few days, if lowering the abn to 5000 would help onboard new users.
Moving on however to my more important point, Im thinking we code in a server side GSC campaign for Rosetta, using our new GSC system, and vote on it once completed to consume a certain % of the POG budget.  Im thinking we remove POG and switch back to Rosetta - simply because - I feel that people are very apprehensive to tithe (give to the foundation to mine) - I think they find it very unusual to be coaxing people to give to the foundation in order to receive POG rewards.  However I think some people do like the 'interest' component of pog, so what we can do is vote on 'how much of pog would be rosetta' and leave a few % points for interest.  For example, maybe we keep cameroon-one as-is, leave 5% for healing, and with the remaining 45%, we go with something like 40% for boinc and 5% for interest bearing balances etc. 

One thing this would do is allow us to simplify the requirements as far as unlocking the wallet and requiring a "payment" to go to the foundation, we just need the daily update to be sent.  Im thinking we look into 'free transactions' also, as it may be possible to send those with a locked wallet to simplify those updates.

Then soon in our next release, we will also have chainlocks.  The Sanc reward is going up a little and the heat mining down, but this should work perfectly with chainlocks as security is guaranteed in the next branch.

Regarding the plan for the external miner, I will be posting binaries for linux (x64) and Windows x64 tonight.  I have no idea how the benchmark will compare to our inbuilt miner so this should be fun for all of us.  In order to use the new miner, you must also upgrade biblepay-qt (as there is a stratum call in the next version you need).  Ill post instructions on how to run the miner also.  If people need binaries other than these two, lets ask MIP to jump in and see if he can help release some extra build scripts.

We just got listed on Needyex.com.  Ive sent them the addl collateral, so feel free to test the exchange out.

Ive had a few exchanges reach out to us this week, some with very high offers that are out of the ballpark - thanks for initiating these Togo.  So far, gate.io declined to list us for "an unknown reason" but invites us to reapply again next year.  Ill summarize these asap. 

Please look forward to BBP leisure upgrade for mining in a few hours  - we can test the new external miner.

Regarding GPU/Asic, once we start mining on this new external miner (bbp-miner.exe), we look forward to anyone who has GPU capabilities to try to port us to GPU (or asic).  I want to see transparency here in our project - I want a good honest white hat hacker to give it a shot.  There are interesting dynamics here - due to the low POBH reward, but nevertheless we need to know if anyone can do it for the sake of the whole community.

On a side note:  in this phase the external miner will *only solo mine* you cannot pool mine with it.  The goal is to benchmark it, and if its faster than the core client, I will move on to making a stratum pool.  I still want the stratum pool to handle future scalability and maintenance in BBP, to replace the c# server side pool code.  We will just keep the orphan letter writing in the pool, and then move that to DSQL when we have time - then we can take down pool.biblepay.org, and just have p2pool and DSQL running.  Then volunteers can make Nomp or whatever pool they want later off of p2pool as a template (or simply run more p2pools) etc.

Actually the evodb corruption error means the erase chain was not done (evo db should have been cleared along with blocks).

Try this:

./biblepay-qt -erasechain=1

Let it completely sync before looking the balance; ensure it is actually synced to the top block.