Yes, unfortunately I was able to reproduce this issue. Fortunately the exchanges usually dont use this command by default, so I think we can patch this without wreaking too much havoc.
C-Cex shows difficulty on top-right of the trading BBP/BTC pair page, but I don't know if it comes out from that command or from getinfo. Meanwhile I will compile 1.1.8.5b for MacOS and also prepare ubuntu PPAs BTW I upgraded my sancs to 1.1.8.5 from PPAs without issues, I didn't even need to delete blocks/chainstate data except in one of them (I could have shut it down unproperly). sudo add-apt-repository ppa:biblepay-official/mainnet
sudo apt-get update
Packages for Biblepay mainnet (stable).
Distros: 16.04 (xenial) and 18.04 (bionic)
Architectures: i386, amd64, armhf, arm64
sudo apt-get install biblepayd # daemon and cli
sudo apt-get install biblepay-qt # for QT GUI
|
|
|
|
|
Rob, regarding PoG, some questions that will surely be of interest for our community and investors:
- how will the reward distribution be in terms of %?
- Will tithes replace the monthly 10% superblock for orphans or will it add up?
- Will masternode owners keep on having the same share as miners/tithers?
Thank you for the great job.
|
|
|
|
Android wallet update on Google Play StoreDownloadSome users reported chain sync problems so we added a few more nodes, updated checkpoints to those used in the Core wallet, and also updated to latest Android NDK for compiling. New version (214) should take a few hours until it propagates to all Google Play servers. Until then older version (213) will be available. You can see the version in "Settings -> About Biblepay screen" (below)
|
|
|
|
1.1.7.7 - Leisure Upgrade
- Added WIN exit handler (in getboincmetrics during initialization) - Test to see if this stops crashing in Win10 Home (be sure to set boincmetrics=0 first)
It works! (Win10 Home, 1.1.7.7, boincmetrics=0) If a problem arises when invoking boinccmd in Windows, now you will see a line in debug.log similar to this 2019-01-03 08:20:04 ERROR WinAPI CreateProcess failed (code X) being X the windows error code number. https://docs.microsoft.com/en-us/windows/desktop/debug/system-error-codes--0-499- |
|
|
|
It might be due to the way we handle our masking of the flashing boinc command window - not being compatible with win10 Home -
I'll jump in and add a switch right now to allow you to disable that feature and then you guys can tell us if it fixes it.
This will take a while to compile; hang on.
1.1.7.6 is out there, anyone who crashed on Win10-home will you please test to see if the problem was the initializing boinc windows? Please add this to the config file: boincmetrics=-1 (-1 means dont try at all, 0 is the default, and 1 means try the legacy way (IE visible command prompt windows)). Thank you. Just tested it and -1 works, while 0 and 1 produce the crash. 0 is expected to produce the crash, but strangely 1 is also crashing. I'm preparing some alternate call with error handling and some logging. I'll keep you updated. |
|
|
|
This version crashes on my home computer, which is Windows 10 Home 1803 x64. This is debug.log:
Does it crash always or occasionally? This morning it crashed on me after a couple of hours on testnet but I cant reproduce this on main net If we cant find a pattern I can add some logs to win32 ShellCommand call to boinccmd just in case. |
|
|
|
BiblePay 1.1.7.5
Leisure Upgrade
- MIP fixed issue where autounlock fails to lock wallet
- MIP fixed issue with black flashing windows in WIN when calling for boinc results during boot
MacOS DMGs are ready and Ubuntu PPAs at biblepay-official are building now (for both mainnet and testnet). |
|
|
|
I read this from CriptoBridge Discord channel: BBP deposits and withdrawals are DISABLED No reason though. Edit: I found this from yesterday BiblePay: BBP
Deposit/Withdraw: Closed
Message: Disabled upon developers request.
Withdrawal fee: 0.01 BBP + BitShares blockchain fee
Required Confirmations: 250
But it's strange that they announce it today. |
|
|
|
if i understood it, then 100% cpu mining i needed only if you want reward for finding blocks. in other cases, you just need tithe something and then waiting in idle for reward (or very very low cpu set to mining as now with gen=1)
You got it right. As I mentioned before, in crypto jargon we would say 20% PoBH + 80% pooled PoS. Tithing is the "pooled PoS" part, because your stake (tithe) is not only valid for the next block (as in plain old PoS), but it counts for a 205 block (24h) period. |
|
|
|
|
The way I see PoG2 is as PoW (PoBH) + pooled PoS (the "tithing" part), with a 20%-80% reward ratio respectively.
After some meditation I think it can really help us kill three targets in one hit:
- simplify usability
- removing the need of an external pool (through the internal pooled PoS process).
- remove dependency on an external oracle process (BOINC)
So technically speaking it's a very good idea. Perhaps it was necessary to explain it in more simpler terms.
For me it keeps the best of PoW world and adds a new dimension to PoS (I haven't heard of any other alt coin with internal pooled PoS, only external).
Another point of the discussion is that, even if PoG2 it's a good idea, whether the moment is right or not. It's hard to say. Probably if we were on the good old times we would say "it's fine, don't touch it!". So this would make bad times (like the ones we are in) much more suitable for changes.
|
|
|
|
|
BBP price spiked to 24 sats in SouthXchange a few hours ago, let's hope we have more of this action in the coming weeks.
|
|
|
|
Such things happen. I will be excited and optimistic when I see buy walls @ 10,11 satoshis, not hit-and-runs like yesterday  Although there is a lot of road ahead, the increase in volume is a good sign, |
|
|
|
|
As I have expressed to Rob in past communications, I am more aligned with PoW philosophy, which is the one that one took BTC from $0 to $19k.
This is what someone mentioned above: only what costs unforgeable effort adds real value.
This does not mean that we can't discuss and explore new concepts, I think it's better than doing nothing for months which is what you see on the other 99% altcoins.
In this sense, I really appreciate Rob's efforts.
Regarding Biblepay's rebase with Dash, status of code rebase is 64% of the command line daemon and client (QT UI will be left for later on).
I'm leaving miner stuff for the last phase to avoid rebasing code that might change.
After pure code rebase I see these tasks:
- Review with Rob all the biblepay code conficts with new Dash features (DIP2, 3, 4)
- Then try to compile biblepayd, biblepay-cli
- Create a workable devnet.
- Meanwhile in parallel start the QT rebase effort.
- When devnet is working, move on to testnet and check through the masternode migration plan, to test that each step is flowing fine.
Every task in this list will require considerable time and effort, but it will be well worth it I think.
|
|
|
|
In windows, the shadow command prompts (they appear but no logging and messages) is a little unnerving. It can appear as malware like behaviour.
I think the earlier we can exploit in testnet, you'll reduce the cheaters in production.
I think you mean the background boincmd calls. We are currently using POSIX type call popen in Windows and Linux to shell execute, so they might have some weird behavior in windows. But I think I can replace them with Win32 shell command call to prevent this behavior. IŽll check it. |
|
|
|
IŽll make a copy of those later so both PPAs compile.
Does this mean I can stay on the "biblepay" PPA now that you manage it? In any case, thank you very much for your work, I have just installed Ubuntu 18.04 on my main server and I was wondering if the PPA will work, because I've read that 16.04 is still better / more compatible to use for Bitcoin based coins, mostly because of the libdb. I will try to maintain it but at some point it won't make sense to have 2 ppa's The idea is to have mainnet for master branch and testnet for develop branch releases (so a testing cycle does not interfere in stable versions) Later on when we merge with current Dash we will have to move to its fixed depends system. I don't know how compatible it will be with Ubuntu/Debian way of doing things, but I guess we will make it work one way or another. 16.04 version is better for masternode stability, as the libs don't have leaks. 18.04 do have some leaks and biblepayd crashes after 2-3 weeks on 1GB VPS. For desktop use 18.04 is also fine. |
|
|
|
running into a problem installing the linux/ubuntu wallet: ... on ubuntu desktop 18.04.1 the error is from installing from the ppa:biblepay-official/mainnet Solved |
|
|
|
running into a problem installing the linux/ubuntu wallet: ... on ubuntu desktop 18.04.1 the error is from installing from the ppa:biblepay-official/mainnet I'll check it and come back later, we install libdb4.8 from an external source dependency (bitcoin repo). Quoting myself... there seems to be a problem with libdb4.8 build at bitcoin PPA (too old for 18.04 and it misses another dependency). I guess that's why Licht added a custom db4.8 package for that purpose - which does work in 18.04 IŽll try to re-build using this custom db4.8 BTW Licht stable PPA does not compile now because build expects some icon files I renamed from dash to biblepay. IŽll make a copy of those later so both PPAs compile. |
|
|
|
running into a problem installing the linux/ubuntu wallet: sudo apt-get install -f biblepay-qt
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help resolve the situation:
The following packages have unmet dependencies:
biblepay-qt : Depends: libdb4.8++ but it is not installable
E: Unable to correct problems, you have held broken packages.
on ubuntu desktop 18.04.1 the error is from installing from the ppa:biblepay-official/mainnet I'll check it and come back later, we install libdb4.8 from an external source dependency (bitcoin repo). |
|
|
|
|
Show Posts
