|
Almost 27M BBP 24h volume on SouthXChange, this is good sign.
Edit: 45M now!
|
|
|
|
BiblePay
1.4.3.4-Leisure Upgrade
** Mac & Linux building, Windows released **
** Mac & Linux Ready ** |
|
|
|
For ARM: the new version works if you have Ubuntu for ARM installed, but it fails for armbian: Linux odroidc2 4.19.42-meson64 #5.86 SMP PREEMPT Sun May 12 19:04:28 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux Thx.  Yep all the binaries are ready for Ubuntu linux (and probably for Debian), but not for armbian. I'll check if I can do something about it. Edit: from what I read, it should be possible to run ARM version also in armbian. Are you using aarch64 binary? Also, what error is the system showing? |
|
|
|
Edit: the new Linux binaries don't work anymore. The Arch Linux x64 gives an "error in binary file", the Linux 32 can't even be executed (only gives "no such file or directory"), same goes for the ARM version.
Can you please give me details on which platforms you are executing those binaries respectively? Output from should be enough for each system. |
|
|
|
In ubuntu 16.04, double clicking on an unconfirmed transaction causes the wallet to crash. The command line then reads:
Segmentation fault (core dumped)
I believe this is fixed now; I was able to reproduce on my windows box, so I just released 1.4.3.3d; if you compile from source please try it. Otherwise we will have to ask MIP to make a release next. Windows has been deployed. (I tested this on my local machine and it appears to have fixed it). Compiling... Edit: binaries for linux ready |
|
|
|
|
MacOS users
Signature certificate for Biblepay Core Evo wallet DMG file (MacOS) was expiring today, so it has been renewed.
You should not notice any difference, but in case you have problems opening Biblepay Core, please report.
|
|
|
|
BiblePay
1.4.3.3-Leisure Upgrade
** Note: Sancs, please upgrade within 21 days at your convenience **
** Linux and Mac is building **
Mac and Intel Linux (32/64 bit) compiles are ready, ARM (32/64) still building. ARM (32/64) binaries ready. |
|
|
|
BiblePay
1.4.3.3-Leisure Upgrade
** Note: Sancs, please upgrade within 21 days at your convenience **
** Linux and Mac is building **
Mac and Intel Linux (32/64 bit) compiles are ready, ARM (32/64) still building. |
|
|
|
i think that machines with negative hps does not appear in pool... maybe new version fixing this, but i dont have new binaries yet 
1.4.3.2-Leisure UpgradeLinux binaries available at www.biblepay.orgsha256sum *.tar.gz a513d937ca5710c190af63e59f6ad0cb44d39c88a60881b00ad74442e5e51f7d biblepayd-evo-aarch64-linux-gnu.tar.gz e36ba0605f5378b0dd598d12bf990ae96c34a557b52f012c91720863c91a2153 biblepayd-evo-arm-linux-gnueabihf.tar.gz d9346aaf571be1961607795a2ab667b2394970043f11442202aa77281de69d39 biblepayd-evo-i686-pc-linux-gnu.tar.gz 792c674c230d82f3562210f6f0a212e31470fc8231570774766d9518a76b6b5a biblepayd-evo-x86_64-pc-linux-gnu.tar.gz 5c08bb2c1d1ae5ea8451c7f7d2dbddaaa1348191395ec8d7598c9766ea2aa250 biblepay-qt-evo-i686-pc-linux-gnu.tar.gz 42c175551a60bef0faf59470000d07e0f806834f549fdf185dc2c89ab90e339c biblepay-qt-evo-x86_64-pc-linux-gnu.tar.gz |
|
|
|
How do I move the old Sanctuary Wallet and Windows Controller Wallet to the new EVO?
Just copy wallet.dat from %appdata%/BiblepayCore to %appdata%/BiblepayEvolution |
|
|
|
It looks like Licht maintains this; or MIP, would you like to edit this? I think we need to wait for MIP to complete the chiaBLS fix first so then he will know the repo name. I will try to disable temporarily current PPAs as they are related to Classic. I don't foresee a quick fix for a ChiaBLS PPA, because it depends on Relic Toolkit so it's a chain of libraries the ones I have to create in PPA, then create another PPA for Biblepay Evo linked to these other custom PPAs... not easy stuff at least for me. |
|
|
|
biblepay upgrade to Evolution on win10 64bit. how to setting biblepay.conf?
It depends. Do you want to mine or just have a wallet or controller wallet? If you want to mine just add gen=1 genproclimit=4 In second case, you don't need to config anything. |
|
|
|
I think waiting does work in this case, but another way around to be sure is on the Sanc itself, stop it, delete the mnc*.* and gov*.* files and mnp*.* files (just the caches) and restart, and as soon as mnsync status passes 3, I believe your node will be more up to date (with the Sanc list).
EDIT: I don't see you in my Sanc list; try ensuring your controller does not have any banned peers first, then re-start the Sanc (with the Start button from the controller), its possible it needs a new re-broadcast done. It takes up to an hour sometimes to see it change, so this is probably normal.
Ok I did as you said and it didn't work when launching again (node not yet activated), but then I just activated once again from controller wallet and it activated instantly! Thank you so much for all your help. I do know -probably better than anyone else- about the incredible amount of time and effort that is behind this Evo release, and all I can say now is: God bless you my friend. |
|
|
|
If you are lower could you please try resyncing?
I tried resyncing and both controller wallet and MNs are ok now (block 123126, hash 7355d3ef0e69ddbae973912643185bcfe5fbbeef8d30f6726eec8047a89a4e5d) So everything looks great, but when I finally activate the MNs, it says "success" in the controller wallet, and PRE_ENABLED, but in the MN VPS I see $ biblepay-cli mnsync status
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"AssetStartTime": 1559500589,
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
$ biblepay-cli masternode status
{
"outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
"service": "209.250.243.91:40000",
"status": "Not capable masternode: Masternode not in masternode list"
}
} Is this expected and maybe I have to wait some time? (in previous classic it showed "active" right after activation from controller wallet) Also, I checked collateral tx amount and also if it is old enough. |
|
|
|
How is the network status right now?
Yep there is something going on with mined blocks, my controller wallet has rolled back again to 122999 |
|
|
|
|
In my case I also upgraded miners yesterday.
MNs were ok but controller wallet was stuck at 122999 like capulo's. I resynced and now it's ok
biblepay-cli getblockhash 123010
ad6f362c94ff32ebd0875a1686529fb21e5bbb15ab5afc93c8af7310b32bdcc3
capulo, for
error: Could not locate RPC credentials...
Shut down biblepayd, check that you have latest version (not 1.2.0.1), then launch again. I detected that some 1.2.0.1 daemons are not shutting down in a timely manner, so they don't allow new 1.4.3.1 to start. In extreme case you may need a sudo kill -9 PID
|
|
|
|
|
I am noticing my sancs are taking 80% of the memory on 1GB $5 machines of Vultr, which is new (it was normally 30-40%). Some of them have even crashed. I don't know the reason but I suspect of this sudden required RAM spikes.
Is anyone else experiencing a similar behaviour in sancs?
|
|
|
|
|
Show Posts
