Search content
Sort by
Showing 20 of 27 results by Shoko943
I find very interesting the idea of some sort of blockchain "time capsule" where in the future people could look back at the state of the world at one point in time.
Having said that, I don't know what the technical implications would be (such as the impact on the size of the chain, etc) and more importantly, if it still really adheres to the original vision and purpose of the coin (as it would probably become a main function and use a lot of resources by becoming part of the blockchain?).
I think the strength and differentiation of this coin right now is in its vision, target and just the fact that we're just trying to do something that could really improve the lives of a lot of people. We could really build some sort of caritative platform and focus on having a strong community around it.
I think I would really be more interested in developing the website (working on the separation of the pool and the other functions), letter functions/things around the children we're helping (adding photos, being able to send personal letters, improving the interface, etc), the in-wallet prayer requests, the overall appearance of the wallet, governance of our DAO, etc.
Now, I know it must be really exciting to program that news idea and as the dev said, it could just be implemented now and the sanctuaries could decide on its future later on.
Having said that, I don't know what the technical implications would be (such as the impact on the size of the chain, etc) and more importantly, if it still really adheres to the original vision and purpose of the coin (as it would probably become a main function and use a lot of resources by becoming part of the blockchain?).
I think the strength and differentiation of this coin right now is in its vision, target and just the fact that we're just trying to do something that could really improve the lives of a lot of people. We could really build some sort of caritative platform and focus on having a strong community around it.
I think I would really be more interested in developing the website (working on the separation of the pool and the other functions), letter functions/things around the children we're helping (adding photos, being able to send personal letters, improving the interface, etc), the in-wallet prayer requests, the overall appearance of the wallet, governance of our DAO, etc.
Now, I know it must be really exciting to program that news idea and as the dev said, it could just be implemented now and the sanctuaries could decide on its future later on.
Hello Dev,
please post some addnodes wallet out of sync. block stack at 6342 block, no network connectivity attach.
Thank and regards
Okane Satoshi
please post some addnodes wallet out of sync. block stack at 6342 block, no network connectivity attach.
Thank and regards
Okane Satoshi
Is your biblepay version higher than/or is 1.0.3.4?
@ Inblue, Thanks for the complement. Im a noob when it comes to mining. started a month and a half ago.
I think the problem might be at the actual miner and not the wallet. The cmd miners I used does not have GUI exept for Magi. I know The newer ones as of this year has support for AES enabled processors and the like. So maybe it due to those lovely features it might think we are AISIC miners on windows. I am not familiar with Linux, but I have been a fan since ubuntu. I am just putting my ideas out there, maybe it helps dev with the issues.
I think the problem might be at the actual miner and not the wallet. The cmd miners I used does not have GUI exept for Magi. I know The newer ones as of this year has support for AES enabled processors and the like. So maybe it due to those lovely features it might think we are AISIC miners on windows. I am not familiar with Linux, but I have been a fan since ubuntu. I am just putting my ideas out there, maybe it helps dev with the issues.
The code doesn't have anything that tries to "detect" that you're an ASIC and slow you down. The dev is just trying to make the algorithm by itself extremely hard to be ported to GPUs or ASICs.
I don't care about the lower hashrate/payouts, but it's not really "fair" when linux get 2x hashrate on the same hardware. Just wanted to know why 
Guys- Its not getting ignored- we were moving like a steamroller until F7000 hit, and the issue is things have to be prioritized.
Its a higher priority to address Prod issues than "hashrate" issues.
Now it appears the pool is running again without issues so now I can take a look at the hash rate issues across OS.
The pool is storing the OS flavor per miner now, so I should be able to go in and write a report of average speed per OS flavor.
I do see that windows appears to hash at a much slower rate than linux for some reason.
Im seeing 34,000 HPS on my vultr-debian vs 4,000 on my dual CPU xeon windows web server. Quite a disparity there. Definitely unintentional from our engineering standpoint.
Yeah im not asking you to magically fix it over night, just look into it. Thanks
And first devs answer was "7000k"?!?!?
Reall!?! Problem devs created 8 HOURS ago not 8 DAYS.
I get you are angry but compare this coin against other small coins. We have an incredibly responsive Dev. Block 7000 screwed a LOT of things up. It was a major change to the algo. So to fix it, core pieces of the software have to change. This might change hash rates. This is still a very new coin, I'm positive the Dev is looking into it. There have been significant DDOS attacks occurring on this coin and the primary focus of the Dev has been to protect the pool, which is how a lot of newer users mine (and how many people prefer to mine). So he has not had unlimited free time to fix this issue.
In the meantime, you have several options. One, run Linux, which seems to be doing better than Windows on the issue. Two, accept the lower hash rate and live with it until the fix is in, knowing MOST users are doing the same so we're all losing a similar hash rate. Three, give up on BBP, take your CPU somewhere else and come back next year if you want when the bugs are hopefully all worked out. Four, fix the problem and upload the solution to Github.
There was not such problem with 7000block and even ddos. Prolem is with updates, what happend so special that dev must reduce windows hash on last update? BTW even your xeon-w3503_01 have 2x my ryzen 1700X (80% cpu usage, 37ghz all core) hasrate2... do you think it normal. Where all work from my cpu goes?
i don't want unpolite but miner vultr_debian4 is now in top 10 since 2-3 days, before never... who's this machine?(simple answer).
"We have an incredibly responsive Dev" Yes, for linux. They ignore ALL questions for past 3-4 days from windows users about hash rate. I now that bible_pay is running linux and he dont care windows...
BTW im not angry... i want just get atention of devs to get answers for questions that i make and other windows users. I only want to get through their "ignorance wall" ;P
P.S. Do You know why some users(on laderborad) have 8k HPS and 38k HPS2 and other with 36K HPS get also 38 HPS2?
The dev is not ignoring any question nor is he purposely introducing "bugs/limitations" for windows miners. If anything, you're wrong in assuming that biblepay is a linux guy as even the pool is running on windows.
The f7000 algorithm modification has been extensively talked about the past few weeks including why it was/is necessary and its consequences. There was major issues when it went live so our dev was busy dealing with all of that and I think he did an admirable job in dealing with that chaos. He was also busy fixing the pool and dealing with DDOS attacks so that you could still keep mining using it.
Finally, performance is something difficult to understand as there are so many factors affecting it; from your CPU, memory, disks, internet connectivity to w/e is running on your machine and could interfere with the mining software) and we're talking about a brand new algorithm on top of that! It could even only be an issue with how the hashrate is calculated VS your actual performances.
The performance issue on windows has only been there for a few days and Robert (biblepay) said that he is now looking into it. It might take a long time as troubleshooting performance issues on a specific platform is not an easy task.
There was a new mandatory a few days ago so 1.0.3.4 and above would be the "correct" version.
You may want to try to to delete the "blocks" folder and "chainstate" folder.
I'm not sure about it but it could be possible that all the other nodes temporarily banned you since you were spamming them with the wrong version.
You may want to try to to delete the "blocks" folder and "chainstate" folder.
I'm not sure about it but it could be possible that all the other nodes temporarily banned you since you were spamming them with the wrong version.
Ok, so the 900K i mined on the other chain is worthless I guess? Deleted the blocks folder and chainstate, downloaded an installed 1.0.3.5, and all those coins are "gone" from my wallet.
Yup unfortunately
Did you manage to get your wallet to sync again?There was a new mandatory a few days ago so 1.0.3.4 and above would be the "correct" version.
You may want to try to to delete the "blocks" folder and "chainstate" folder.
I'm not sure about it but it could be possible that all the other nodes temporarily banned you since you were spamming them with the wrong version.
You may want to try to to delete the "blocks" folder and "chainstate" folder.
I'm not sure about it but it could be possible that all the other nodes temporarily banned you since you were spamming them with the wrong version.
still dont understand that my 2CORE/4HT G4560 is same like my RYZEN 1700 8CORE/16HT gpuproclimit setup 2CORE= 8 and RYZEN =16 hash same ca. 8500 
switch to linux
it looks that this coin is only for the chosen ones .... and even the BiblePay itself does not know how it works
wthell is testnet? we have except pool (which doesnt work) anything yet?
this is frustrating for me how this all doesnt work
and yesterday i was on funeral and thinking about biblepay tootestnet is just the testing chain to be able to test things such as new features, bug fixes, etc.
There is a guide on the reddit on how to compile and run it on linux. https://www.reddit.com/r/BiblePay/
Also, your comments can also come across as frustrating.
You first started by trashtalking the coin and the developer, then begged for help because you changed your mind and actually wanted to mine it. You dmed me and I took the time to answer all your questions. People on the public forum also tried to help you. So no, I don't think this coin is "only for the chosen ones".
Finally, I wouldn't be surprised if a lot of people started to ignore you.
Is there anyone to talk with c-cex about endless wallet maintenance?
When will be available the wallet c-cex.com??? I wrote "Maintenance..."
C-CEX is waiting for us to give them green light to upgrade.I want to ensure the ReadBlockFromDisk error is Dead before I green light them.
Overnight, I made an update internally to the pool server with new code. Now I am burning it in.
We will have to wait until I have time to parse the logs and ensure the error is dead.
Hello, Am I on the wrong chain again? Even my ancient dual core is getting ridiculous amount of blocks solo mining. I hesitate to say just how many today. I am getting confirmations, but this behavior is odd. Its raining blocks and it hasn't been like this in a long while.
I am on 1.0.3.1 (64-bit) and at this time on Block 7671.
I am on 1.0.3.1 (64-bit) and at this time on Block 7671.
Biblepay 1.0.3.4-Mandatory Upgrade
www.biblepay.org
- Fix ST13 Error
- Fix f7000 Low-Subsidy based on High-Diff calculation
- Fix Pool banning issue
- Fix Read Disk error
- At block 7500, we raise the subsidy back to ~18,000.
You're on the wrong chain. There was a new mandatory 2 days ago.
So on the ST13 error, I see we have a line of code for DGW that is strictly used to log to the screen and it could potentially be causing the ST13 error.
I commented that out, and pushed 1.0.3.3 out. Anyone on Linux that has this ST13 error, please upgrade to 1.0.3.3 and let us know if that fixes the ST13 error.
Ill build a new version of Win just in case.
I have to run a few errands, windows is building now.
Regarding the Ban issue: This new version will ban 1031 and down, because the subsidy is higher. We will just have to wait until everyone upgrades to 1033 to test the ban issue to make sure its gone.
I commented that out, and pushed 1.0.3.3 out. Anyone on Linux that has this ST13 error, please upgrade to 1.0.3.3 and let us know if that fixes the ST13 error.
Ill build a new version of Win just in case.
I have to run a few errands, windows is building now.
Regarding the Ban issue: This new version will ban 1031 and down, because the subsidy is higher. We will just have to wait until everyone upgrades to 1033 to test the ban issue to make sure its gone.
Welp, just got the ST13 error too on some of my miners, I'm upgrading now.
How long is the ban supposed to last? I was wondering if I could end up having everyone banned on my miners before they upgrade and have them still banned after they upgrade? and if this happens to everyone upgrading now, could we end up with the same situation that happened with f7000?
I just finished upgrading to 1033 and I'm still getting the ST13 error.
************************
EXCEPTION: St13runtime_error
tinyformat: Not enough conversion specifiers in format string
biblepay in ProcessMessages()
So on the ST13 error, I see we have a line of code for DGW that is strictly used to log to the screen and it could potentially be causing the ST13 error.
I commented that out, and pushed 1.0.3.3 out. Anyone on Linux that has this ST13 error, please upgrade to 1.0.3.3 and let us know if that fixes the ST13 error.
Ill build a new version of Win just in case.
I have to run a few errands, windows is building now.
Regarding the Ban issue: This new version will ban 1031 and down, because the subsidy is higher. We will just have to wait until everyone upgrades to 1033 to test the ban issue to make sure its gone.
I commented that out, and pushed 1.0.3.3 out. Anyone on Linux that has this ST13 error, please upgrade to 1.0.3.3 and let us know if that fixes the ST13 error.
Ill build a new version of Win just in case.
I have to run a few errands, windows is building now.
Regarding the Ban issue: This new version will ban 1031 and down, because the subsidy is higher. We will just have to wait until everyone upgrades to 1033 to test the ban issue to make sure its gone.
Welp, just got the ST13 error too on some of my miners, I'm upgrading now.
How long is the ban supposed to last? I was wondering if I could end up having everyone banned on my miners before they upgrade and have them still banned after they upgrade? and if this happens to everyone upgrading now, could we end up with the same situation that happened with f7000?
Sorry to add to the list too but I have noticed that my upgraded miners were banning a lot of people. Could we get the same issue of us banning each other or is it just a coincidence? I have never really paid attention to it before.
Please be ready for a mandatory upgrade in 4 hours.
I was born ready.
Awesome work, very fast.I see 1.0.3.2 is already on GitHub, so we can start the upgrade?
This way we can all sort of get in together.
I started linux upgrades. they will take at least an hour anyway . thanks Bible_pay
Yeah, "make" takes around half an hour on high spec machines. Is there a way to only build changed files, like src/main.cpp and src/pow.cpp?
sorry to say , but 1.0.3.2 on linux is dying the same way as 1.0.3.1 . have to follow the same routine restarting the daemon
I just upgraded and I have had no issues so far. I'm running Ubuntu 17.04.
guys: can i mining with 2 machines to 1 wallet? or every machine must have own wallet always?
There's a wallet.dat file in your BiblepayCore directory (usually ~/.biblepaycore on linux or /AppData/Roaming/BiblepayCore on windows). Just copy whatever wallet.dat file you want to use from one machine and place it in the BiblepayCore directory on the other machine.
Yeah, I havent actually done that myself yet, but I have 'one' piece of info on that. Blue said he copied his one wallet.dat file over to 10 machines, and now on his desktop he receives notifications when any machine mines a block (IE the txlist updates). So he has one consolidated wallet.
I was going to add: In POW, since coins can be received in a locked wallet, you can encrypt and lock your wallet and still receive rewards from any POW device out there mining into that single wallet.
I have some experience with this. The only thing you need to be careful with is not to "run out of keys". The wallet file has 1000 pre-generated private keys with biblepay that are used for every new address you generate. Once you used all the keys, it automatically starts generating new keys for the new addresses.
So if you start mining on a lot of PCs and they suddenly run out keys and start generating new ones, the wallet.dat you kept may not contain these new keys!
The way to mitigate this could be to start with a wallet.dat with a bigger pool of pre-generated keys (can do that with biblepay-cli keypoolrefill x where x is the amount of pre-generated keys you want. You need to be careful as you wallet.dat file can become quite big!)
What block are we currently on? I wasn't around yesterday so I just saw there was another mandatory update just now. The block explorer is still running 1.0.2.9 so it might need to be reindexed. Compiling 1.0.3.1 right now.
I just noticed about it once you mentioned about block explorer, I thought it was updated, and I went to check the block height, it seems like 30 blocks away from current height. And no wonder it shows block reward of full 20000, if I'm not mistake it should be 199xx...
Currently the reward on the new chain is actually way less than that. I'm not sure if it has to do with blocks being mined too quickly? We are actually having a soft fork but it seems it will be successful as I think most of the hashing power is now switching to the new chain.
What block are we currently on? I wasn't around yesterday so I just saw there was another mandatory update just now. The block explorer is still running 1.0.2.9 so it might need to be reindexed. Compiling 1.0.3.1 right now.
I just checked the pool and it's showing 7282 right now.
https://i.imgur.com/c4ECwSr.png NetDiff
https://i.imgur.com/eopzpLg.png OUT OF SYNC on CCEX
where is problem now?
https://i.imgur.com/eopzpLg.png OUT OF SYNC on CCEX
where is problem now?
The dev sent them a message earlier so they can take the wallet offline for now while the issues we have/had with f7000 are being resolved. Also, last time I checked they were still using the 1.0.2.9 version instead of the new 1.0.3.1 so maybe it ended up crashing or couldn't find any connection or something else.
On that note, I would encourage anyone who hasn't upgraded to 1.0.3.1 to do it now