|
I really like masternode coin BiblePay, about to become 1 year old project,
and one of only a few masternode coins with a Monthly Budget and Governance set up and running
|
|
|
|
|
Patience is Key, the markets are volatile,
If you believe in the technology, the team, the strategy, the mission, etc,
Why would you sell if price goes down? You should buy more on discount!
|
|
|
|
Very awesome that Newton coin supports Rosetta@home!, Rosetta helps research for Cancer, Alzheimers, HIV, etc I am curious, Why not use Masternode Monthly Budget System for funding? Interesting project, I will keep an eye on it  Look forward to your white paper! |
|
|
|
|
Woah we got to PODC block 55555 solved it
and then jumped through 55556 to 55612 super fast! like 5-6 minutes!
|
|
|
|
Looks like we are on different chains, I am not sure which chain is the correct chain though EDIT: getblockhash 55513 66440144d097c4517d81fdee3ed87b8bd279d8a38be6e843bd4a196c3a571694 I get same hash as you, looks like we are on same chain  , maybe I was on bad chain previously |
|
|
|
Last PODC superblock was at 55350, next one is at 55555 and we are currently at block 55515, so 40 blocks away, assuming 15 min per block, about ~10 hours away I got the explorer back up: http://explorer.biblepay.orgI think mongodb crashed, added script to auto start it if it does crash ./biblepay-cli getblockhash 55513 6926e8ef326aba351bf0b6c43a3df67a76a30dd1d6c9c9312fa4c3c25c41ec1dUPDATE: 66440144d097c4517d81fdee3ed87b8bd279d8a38be6e843bd4a196c3a571694 So apparently this config option, truncates the debug.log file to 200KB on start if its over 1MB in size shrinkdebuglog=1 https://bitcoin.stackexchange.com/a/35766/30932I have a crontab that starts biblepay every 2 minutes, (it exits if its already running) Ill test and report back if this config option works Theres also a way to set the logfile to /dev/null https://bitcointalk.org/index.php?topic=46709.0 |
|
|
|
Seems there are some folks making the most of the coin..
CPID: 0504c91dac5d2c4156d2a2dd992bcc8f 32 Blocks ( 15% of 206 blocks) 14959.71883359 bbp earned Subsidy: 14944
CPID: ce2a54170bfbb9d6354909c801c3f053 32 Blocks ( 15% of 206 blocks) 14886.6996555 bbp earned Subsidy: 14871
CPID: 6d3cf73125be19efe95f073575990d70 14 Blocks ( 6% of 206 blocks) 6656.12902918 bbp earned Subsidy: 6647
15% is the highest i've seen thus far. (this is top 3 from the last days worth of blocks)
I almost wonder if #1/#2 are the same person (2 separate CPID's, but similar patterns low RAC consistently low stake)
For perspective, purepool is currently mining 14% of blocks
Is this from Proof of Work (PoW (Heat)) Mining? Isnt heat mining a bit more dangerous because you have to copy your same wallet.dat to all your machines? (and then you have to set utxooverride=-1 on all the additional PoW miners so they do not send PODC Updates) (because in order to PoW mine you still have to do a little Proof of Distributed Computing (PODC (Research)) mining) == Rosetta@Home is dominated by BBP and Onii-chan https://boinc.bakerlab.org/rosetta/team_members.php?teamid=15044&sort_by=expavg_credit&offset=0 |
|
|
|
Does anybody know when the next mandatory release is coming? If I remember well it is supposed to happen soon.
Rob pls regarding the mandatory update what is the date planned for update?
The Status is generally good, I suppose I would give it an 80% tested rate, however there are a couple small but important things that need more testing. So in general, I feel that we do not have enough lead time to make the 6-27 (monthly superblock deadline) to rush a release out. However I think we will be wrapped up within 14 days. This gives us a chance to get in any last minute changes also. It will probably be released around July 14th.
I know CryptoBridge is waiting, so during the next release we will need to start using the Github releases feature also. (This allows bots to see that we released a new mandatory upgrade). Testnet Testing Thread: https://forum.biblepay.org/index.php?topic=190.0 |
|
|
|
|
Leave if you do not believe in the technology
I am staying
|
|
|
|
My masternode (sanctuary) also crashed recently, nothing stood out in the debug.log I ended up deciding to use crontab to run BiblePay every 12 hours (if BiblePay is already running, the new attempt to run it detects lock and fails/exits) sudo crontab -e
0 */12 * * * /home/biblepay/src/biblepayd > /dev/null 2>&1 biblepay.conf already has dameon=1 in it, so no need to pass any parameters Im wondering if I should start enabling all the debug flags so I can try to catch any problems? is the only concern that my debug.log would fill up a lot faster? (I could have a weekly log file reset script) Just curious, Do exchanges auto restart wallets if they crash? |
|
|
|
I contacted them about this already, they didnt change it, sent another request couple days ago I hope all is well Licht |
|
|
|
|
Show Posts
