Please stop the name-calling, it looks foolish.
I understand that people is invested in BBP and lower prices are a concern for everyone. Knowing that this is a cyclical pattern in the crypto/alt-coin world does not help relieve the pain. However there is only one formula that has worked in the past and will work in the future, which is sticking to the plans, keeping the values strong, and try to offer higher value to the coin project, even in ever changing environments. Currently the money is out of the markets and it does not distinguish between the gold and the iron, the worthy and the scam. It's happening to practically all coins. The only way to survive is keeping up the good work, so when the money comes back to town, we are there in the first places in terms of technical development, governance and accountability. |
|
|
|
Thanks Togo. I would highly discourage our community to operate with C-Cex, at least on a daily basis, because of their unprofessional practices (this is not to call things for it's name, scam). If you need to operate there, try to keep your balances empty at every moment, then transfer your coins, operate, and withdraw the proceeds as soon as possible. This way you will minimize the chances of living the nasty experience of seeing your balances wiped off some random day. |
|
|
|
|
I think we will reach higher levels of compliance and accountsbility with The Biblepay Foundation, and hopefully will also release Rob from some unpleasant paperwork.
|
|
|
|
C-CEX just posted that their DOGE and LTC accounts got hacked and all the balances are gone. I think the exchange is in semi-maintenance mode. Tried to withdraw BBP to different wallet addresses, but error keeps saying invalid addresses. Anyone else have trouble doing withdrawals of BTC and other coins?
Similar thing happened after christmas "holidays" with Verge coins. These C-Cex guys are either inept or thieves, I would bet the latter. |
|
|
|
Thanks. I enabled the Requirement of running watchman on the wall.
Technically, within 24 hours, all the masternodes in WATCHDOG_EXPIRED state should fail to be paid (as the sancs vote for each other).
It is clearly working. At the beginning, payment frecuency rised to each 24h (from 36h), and now it's on 26h as MN users slowly fix them. |
|
|
|
|
Almost every masternode coin is exactly at the same market situation: no buy orders, no money. This is not a BBP only problem.
We must keep on working and make a difference when the tide turns.
|
|
|
|
Please provide one watchdog expired masternode who is in the upcoming masternode winners list.
Looking at the code, we are no longer voting for those masternodes.
At this very moment (block #68247): Block 68247: BTFT5kkUDwDg7KWpd7snL1BZAN5KgemRsN Block 68256: B7SvqHBccPR8iYTq8rbjzpEqiGFnAT8hGg Block 68257: BQ1QoPAtgEoZRkDv8s5Jf4qnCoWLwgspH1 All these are seen as WATCHDOG_EXPIRED in Biblepay-Central. However in my desktop wallet they appear as NEW_START_REQUIRED. This could be some delay or glitch in biblepaycentral monitoring. |
|
|
|
According to biblepay-central, there are 213 enabled masternodes. The rest are mostly in states like 'NEW_START_REQUIRED' or 'WATCHDOG_EXPIRED'. And now the WATCHDOG_EXPIRED nodes don't get paid, so they will probably be taking them offline or fixing them soon. Still MNs are getting paid about every 36 hours which fits best with an active number of 300 rather than than 210 (that would mean a 24h frecuency). |
|
|
|
Hey!
I'm trying to update the core from last github update, but when I finally execute "make", the server is stuck at 'CXX libbitcoin_server_a-kjv.o"
Is it normal to wait for ages? The server is with Ubuntu 18, with a 2 Ghz 1 cpu proc and 1.7 Go RAM. Not very powerful, but I wanted to use some spare resources..
And it worked for the previous version, but I'm not sure it took so long.
Thanks for your help!
With less than 2GB it can take like 15 minutes or more, that's normal. |
|
|
|
Hmm, I think your OK on the first error, that means it tried to clean the chain and couldn't so it tried to reboot (and couldnt because it was launched from an absolute path).
On the 2nd error however, someone will need to run that version in valgrind and give me the line # of the 'double free or corruption'.
EDIT: On #2: I believe I just reproduced the error. Please upgrade to 1146h.
Some MacOS users reported this problem too 1.1.4.6h for MacOS is ready on biblepay.org wallets setion. |
|
|
|
One huge side benefit of this, is this IPFS protocol allows the build-out of the new decentralized web. IE you can click browser links in the future based on files stored in BiblePay. (That feature might add large value to BBP in the future).
In fact some other masternode coins are planning to offer IPFS as a core incentive for the coin, and many of them will probably take months to deliver. Having this implemented in Biblepay would be a mind-blower feature indeed. |
|
|
|
BiblePay - 1.1.4.6f
Leisure Upgrade
- Merge in Mac compiling change to crypter.cpp
- Prevent crash in getchaintips
- Modify Sanctuary business logic to help ensure the chain stays synced
- Add HealthCheckup feature to help recover during a fork
- Add deterministic ddos of invalid blocks to help prevent ddossing good nodes (help prevent forks)
I highly recommend sancs upgrade to this version within 7 days to prevent future forks. Also any normal user who goes out of sync, please upgrade to the latest version.
MacOS version also ready (compatible with 10.12 and 10.13) Ubuntu 18.04 users: This version should finally compile as it is compatible with both libssl 1.0. and 1.1. |
|
|
|
Did these sancs in question crash, or fork, or are they still synced guys?
In my case one stopped and the others were stuck on that block, still running. I had to do a -rescan and it was ok. |
|
|
|
|
It seems there is another strange block around there, half of my MNs have all stopped just at 65736 and then expired.
|
|
|
|
Bitcoin is not particularly much down in price, but the token of this project has fallen quite strongly and this indicates the attitude of developers to the project. I hope the developers do not think about it.
Do your research right and don't just drop a templated one-line post. All masternode coins (not "tokens" by the way) accumulate a 75-90% fall on average. Biblepay only a 50%. MIP, he is spamming to get his signature advertisement into the thread... Yeah I guess, thank you. |
|
|
|
Bitcoin is not particularly much down in price, but the token of this project has fallen quite strongly and this indicates the attitude of developers to the project. I hope the developers do not think about it.
Do your research right and don't just drop a templated one-line post. All masternode coins (not "tokens" by the way) accumulate a 75-90% fall on average. Biblepay only a 50%. |
|
|
|
Hi,
could somebody please check whether I am running on a fork or what has happened?
I imported your address as watch-only and see the right balance (the same seen on the explorer) What wallet version do you have? # biblepayd --version Biblepay Core Daemon version 1.1.4.3 This version should be ok. It seems it's only counting the transactions from to 11th Aug onwards (which sum 55786) but not the previous ones. Try to check if your machine finds this transaction (one of the missed ones) getrawtransaction edcdb5a88e17a61d59b52e093f7535af00352faa4dc672a2517b048a9a343406 1 And also try to restart the daemon with -zapwallettxes=1 option to try to recover those unaccounted transactions. |
|
|
|
Hi,
could somebody please check whether I am running on a fork or what has happened?
I imported your address as watch-only and see the right balance (the same seen on the explorer) What wallet version do you have? |
|
|
|
|
Show Posts
