grcpool just merge mines BiblePay, sells it, and they call it a day. they had a poll and the GRC community wanted BBP sold and not staked. So, not enough community backing to stake BBP. I don't know if anyone at BiblePay team bothered to talk to grcpool operator. Overall, I think removing team requirement backfired and BiblePay's marketing point about "cancer research" lost a lot of steam. The sell pressure from grcpool means charities will support fewer children because the price of BBP is so low. BiblePay will keep dropping until it matches GRC price in terms of payout per RAC.
So, I really hope and pray. If it is God's desire that Proof of Giving (PoG) succeed, let it be so.
That is some important insight, thank you. Considering that it seems it would be better to switch to POG sooner than later (although I have no idea yet what POG is or how it works^^). @Rob: just tried again and an "instant send" deposit to the pool arrived after the 6 confirmations (as shown in the wallet), which took about 5 minutes. So it's definitely a significant difference to a withdrawal, which happens on the instant. |
|
|
|
I tested the pool deposit with 3 small transactions (2 instant send, 1 normal send). It actually took quite a while for them to arrive, but now they show in my transaction history on the pool, so I think it worked. I just never saw them as "pending" in the deposit menu, but to be honest I stopped checking after 5 minutes or so and just checked now (after more than an hour).  |
|
|
|
Quick question about the pool: I tried to withdraw some BBP from there, chose the amount, clicked "send" and received the usual e-mail. However, when I click on the link in there, I always get redirected to a page with a single sentence: "Please wait until January 1, 2021 before withdrawing more than 1001 BBP."Since when is this restriction enabled? What is the purpose of it? Why is this not stated as soon as you want to withdraw it from the pool? It would be nice if you could either remove this restriction OR increase the percentage of the auto-withdraw. Because right now my coins keep piling up on the pool and it is really tedious to pull them off there in 1k batches. Hi Dave, I'm committed to making it work properly. For higher security however, I do feel we should work on auto-withdraws first. Do you have that feature enabled? I will work with you to ensure it either works or figure out what error it failed with. The raising of the withdrawal limit is secondary - I confirm, this limit was added recently due to what appeared to be someone making a hacking attempt. Looking at the logs, auto withdrawals have been working on pool.biblepay.org and they went out today, and most people are using them. Dave, you might have to populate your receive address and click Enable Auto Withdrawals. They go out every morning at 9AM CST. Hi Rob, yes thank you, auto-withdrawal works fine for me and has done so for the last couple of months. But I used to manually withdraw coins additionally, because the auto-withdrawal is set to too little coins (or a too low percentage), meaning without manual withdrawals the coins keep piling up on the pool. I think the most simple way would be to increase the amount of coins for the auto-w. for balances of - let's say - over 1000 BBP. That would be perfect. |
|
|
|
Quick question about the pool: I tried to withdraw some BBP from there, chose the amount, clicked "send" and received the usual e-mail. However, when I click on the link in there, I always get redirected to a page with a single sentence: "Please wait until January 1, 2021 before withdrawing more than 1001 BBP."Since when is this restriction enabled? What is the purpose of it? Why is this not stated as soon as you want to withdraw it from the pool? It would be nice if you could either remove this restriction OR increase the percentage of the auto-withdraw. Because right now my coins keep piling up on the pool and it is really tedious to pull them off there in 1k batches. |
|
|
|
Hey guys, today I installed a VECO masternode by following your script/instructions. A couple of things/problems I noticed: 1. You ask the user for the IP of the server it is running on. This is superfluent and could easily be implemented into the script (e. g. with $(curl --silent ipinfo.io/ip) ). 2. The instructions tell the user to generate the mnkey on his local wallet, then paste this into the script when it asks for it. This imo is wrong. (I tried it your way and the MN was never found on the blockchain). The correct way to go is: install VECO on the server, then the script should do the veco-cli masternode genkey there and paste this as a line into the config (also automatically, same as IP). Other than that it worked. If you need some more ideas, just look at the mn install scripts of other coins (e. g. Biblepay, Carebit, Artax, Wavi ...). Finally, it would be really nice and helpful, if you could register your coin on nodecheck.io.  |
|
|
|
|
Hello all.
I just discovered this coin today. If I understand this correctly, this is a rebrand of a fork from a fork from a fork of Monero.
Maybe this is a silly question, but are holders of XMR and XHV eligible to get their share of XWP? If so, what would be preventing them to dump their load as soon as this coin is hitting an exchange?
|
|
|
|
Hi Dave,
Thanks for the info - Ill delete the spam prayer.
On the unlock issue can you tell us how many threads you are running in the miner and what OS that particular wallet is?
Thanks
Thanks Rob. The problem occurs in my Windows 10 Pro wallet (x64), currently version 71 (but not limited to that version). The config looks like this: shrinkdebug=1
gen=1
genproclimit=4
minersleep=1000
#utxooverride=1463000
#privatesendamount=20000
#testnet=1
pool=https://pool.purepool.org
workerid=B6fo71xAUr2gy2EBxVV69kUDxj7CH6CUXt/pc
#pool=https://pool.biblepay.org
#workerid=dave_pc Maybe it's better to run it with proc 1? I am just running proclimit 4 to distribute the work load more evenly over my CPU. |
|
|
|
Hello all, I hope you had a wonderful blessed Christmas. Here's a screenshot of my windows wallet showing 2 problems at once:  1. Spam-"prayer" with some stupid earning link. 2. Wallet still keeps on randomly unlocking itself (probably related to the PODC updates). This has been an issue (at least for me) for several versions now. I remember posting about this maybe in October. Does anyone else experience this? The only solution I have for this is to manually lock it from time to time. |
|
|
|
Which thousands of people are you talking about? There are around 500 accounts mining for WCG and most of them are pools where the people will never see their bytes or WCG points asset on Byteball (non-transferable), they probably don't even know they would get anything if mined individually. Point of WCG was not to make profit, it's about contributing to something positive like you said. https://wcg.report/It has been just 2 weeks and there are already more addresses (not users) on draw distribution than there was on WCG http://draw.byteball.org/"private untracable" is only the blackbytes asset, which are distributed to newsletter subscribers and draw winners at the moment. That maybe so, but the WCG users are probably NEW Byteball users (which is the actual purpose of a coin distribution ...), whereas the people registering for the lottery are exclusively ALREADY EXISTING Byteball users, which doesn't help the coin at all. Again, try to keep up, the rules for draw lottery have fine-tuned after every week draw (un-attested small holders still have dis-advantage). Latest rules are these, which will increase the chances for other un-attested users again: New rules for the next draw scheduled for Friday Dec 28: 1. Steem attestations with reputation over 60 are now also accepted along with real name attestations. There are only about 3000 Steem users with such high reputation, and many of them have a significant social following. The idea is that it'll help to build referral networks, attract smaller holders, and dilute the whales. 2. The draw has been criticized by both whales who think they are punished with the points system, and by smaller holders who see a large share of points still going to whales. Now the draw is split in two: - one is based on balances, just balances, no points. The winner will be named Prince of Whales. - the other is based on points as before, with rules further adjusted in favor of smaller holders (see below). The winner will be named King of Goldfish ( suggestions about a better name are welcome). The prize fund is split in two: 100 GB for the Prince of Whales and 100 GB for the King of of Goldfish but each participant automatically participates in both draws and can win in each of them (even in both at the same time). Now there can be two referrers, one for the Prince of Whales and one for the King of Goldfish, each receives 100 GB and 211.11 GBB. 3. The new rules for calculating points with the second threshold lowered from 1000 GB to 100 GB: * Real-name attested addresses get 1 point per GB of balance up to 10 GB, plus 0.1 point for each GB between 10 GB and 100 GB, plus 0.01 point for each GB above 100 GB. * Unattested addresses get 0.01 point per GB of balance.* 0.1 point is awarded for each GB of balance increase over the maximum balance in the previous draws, up to a 2x increase. * 0.2 point is deducted for each GB of balance decrease since the previous draw. Say what? 1% is an "increased chance"?  |
|
|
|
For now we are going to reduce the reward to $1 per 1,000,000 WCG points earned, effective from Monday December 24 on. This way the method will still work like a faucet but it will be much harder to make a profit, which was never intended. We’ll monitor what this change does and make further changes when necessary Seriously? I really don't know how your whole distribution policy could get any more stupid. You actually diminish the amount of Bytes for thousands of people who are actively contributing to something (positive) to 1/10 while at the same time keep on throwing away hundreds of GB to 1 (or 2) lonesome users per week? Someone PLEASE explain the mathematical/statistical intentions behind this. Additionally you also diminished the lottery chance for unattested users to an absolute minimum, so practically only the KYC users have a chance. Nice "private untracable" altcoin. Keep up the good work, Russians!  |
|
|
|
|
This new lottery again seems like a good idea executed in a really bad way. Why the hell do you give 200GB to a single person once per week? Why not 20GB to 10 people per week or 2 GB to 100 people per week?
(not to speak of preferring KYC accounts and whales despite the 90% discount ...)
|
|
|
|
Hello guys, just 2 quick questions. 1. The windows wallet (1161) constantly keeps itself unlocked after performing PODC updates. That somehow worries me a bit, I think this was an issue a couple of weeks (or months) ago and already had been fixed, but now it's back. 2. Is explorer.biblepay.org our current (only working) explorer? Because at least for my addresses it shows a lot of wrong transactions and completely wrong overall stats (total sent/received, current balance). For example my PODC address (BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh) is shown to have a current balance of 8 million BBP (I never had anything close to this sum). The total sent/received is in the range of 2 billion BBP (  ). At least this could perhaps be explained by the PODC updates, although those do not show in the explorer. |
|
|
|
tithe_weight Tithed to the Orphan foundation from the wallets internal pool reward system. = will be only 1 pool or more pools? wtf is tithes? who using this shit words? Let us assume we had 1000 participating miners, who tithed 100,000 BBP total this day.
tithed bbp? that description is horrible again  im asked few ppl from our nuclear power plant= engineers,nuclear physicists,supervisors and all told=BBP is waste of time= support any gypsies is waste of time .... use your € for your family and friend nobody understand new way=classic this is easy coin?  bye Wow, once again your language shows the true color of your mindset and obviously also a lot of other SVK guys. I think it would spare the rest of this community (and also you guys) a lot of trouble and nerve-wrecking if you would just sell and wave this coin goodbye. Since you are mining without any electricity cost, every other CPU coin should be "profitable" for you as well ... btt: Unfortunately I currently don't have time to read into the POG thing, but it sounds quite interesting. I'll definitely check it out later this week. One more question regarding the Sancs: How often are payouts expected? My calculation was simply 394MN/205blocks/day = 2 days (between payments). Does that sound right? |
|
|
|
|
Wow, what's going on here? I thought your product was working. Why did this coin lose 80% of its value in 2 weeks, which is way more than most other coins (even the useless ones)?
|
|
|
|
Hey everyone, just a quick question: I have just installed my first sanctuary (yeah!) and started the alias from the Win wallet. The MN wallet status now went from "just started, not yet activated" to " "status": "Not capable masternode: Masternode not in masternode list". Is this normal? My windows wallet states the node as "pre-enabled".
Other MN coins (afair) went directly to "enabled". How long does it usually take for a sanctuary?
P.S.: I just realized that "exec stakebalance" also still states my complete wallet balance and does not deduct the MN collateral. I thought this would be done automatically?
Congratulations btw! So after you update your masternode.conf file and reboot, and you go into coin control, and verify the 1.55M is indeed locked (it should be after a reboot), exec stakebalance will ignore the MN collateral. On the not capable, its 'sort of' normal, but after you reboot, please click START on the gui- restart the sanc, and usually within 30 mins or so it should say PRE-ENABLED. It sometimes takes 24 hours, but that is usually Only when you change IPs... Thx. I did "start all" from the wallet again and also restarted the MN daemon and now it says "successfully started" while the win wallet has it on "pre-enabled". Strangely enough "exec stakebalance" still gives my complete balance, despite coin control and "masternode outputs" clearly showing the collateral to be locked. Ah well, I'll just leave it until tomorrow to sort itself out. P.S.: @MIP: nice work with the MN install script, it even already has the new repository Edit: wohoo, it's "enabled". Looking forward to the first payout. |
|
|
|
|
Hey everyone, just a quick question: I have just installed my first sanctuary (yeah!) and started the alias from the Win wallet. The MN wallet status now went from "just started, not yet activated" to " "status": "Not capable masternode: Masternode not in masternode list". Is this normal? My windows wallet states the node as "pre-enabled".
Other MN coins (afair) went directly to "enabled". How long does it usually take for a sanctuary?
P.S.: I just realized that "exec stakebalance" also still states my complete wallet balance and does not deduct the MN collateral. I thought this would be done automatically?
|
|
|
|
Just for a quick update on the exchange situation; Jaap's just entered a proposal for 2 mil bbp - attempting to pay him back for what he lent us to go live on coinexchange.io. We owe him about .17 btc or so (see the proposal thread for the exact amount). After that, we are free and clear to save up for the next exchange.
We have a really good offer for cryptopia for 1.5 BTC. Its still imo our best next offer (unless something like bittrex appears) - and cryptopia is a hard offer. I think we should take our time and save slowly and try to be listed by the end of 2019.
I just realized that the BBP/BTC pair on coinexchange.io is not listed under the trading places on CMC, livecoinwatch etc. Why is that? It seems to have quite a high volume. Cryptopia sounds good and yes you're right. At our current market cap we really have to take our sweet time to save up the funds. btw: Awesome work @MIP with the ARM repo. Just tested it and it works on both Ubuntu 16 and 18 ARM distros. |
|
|
|
Biblepay 1.1.6.1-Leisure * RPC command 'spork show' improved (thesnat21). * typos and text corrections (sunk818) * changes to support new launchpad PPAs (MIP) Available for MacOS and Linux at this momentDue to unresponsiveness of Licht who maintained the previous Ubuntu PPA packages, we created a new PPA with support for Ubuntu 16.04 (xenial) and 18.04 (bionic) If you want to use this new PPA, and you used previously Licht's package on a machine, please remove it before installing the new packages, to avoid conflicts. # stop biblepay
sudo apt-get remove biblepayd biblepay-qt
sudo add-apt-repository ppa:biblepay/stable --remove
Then add the new repository sudo add-apt-repository ppa:biblepay-official/mainnet
sudo apt-get update
and install as usual sudo apt-get install biblepayd # daemon and cli
sudo apt-get install biblepay-qt # for QT GUI Later on we will create separate packages for testnet versions for that purpose, which will build from "develop" branch of our repo (as "master" branch is used to create mainnet packages). From now on, when submitting pull requests, please select "biblepay:develop" branch as destination, instead "biblepay:master", to allow us to compile and test before moving the code to the "stable" master branch. This will facilitate us managing the whole product cycle more efficiently. Thank you! Awesome work with the new repo. I would really appreciate if you could add ARM branches there too. Those are the ones that are most important (at least to me), since compilation of BBP on these machines takes forever. I really love seeing this community going forward productively and not wasting valuable time and effort in argueing. Let's hope the current bear market won't have too much more downside effect on our beautiful coin. |
|
|
|
How come those vultr servers are so expensive? In Germany we have a hoster where you can get a root server with 2 dedicated cores and 8GB RAM for 7 € per month ... Even if you rent it from anywhere else in the world it's just 9 €! https://www.netcup.eu/vserver/ |
|
|
|
|
Is there a problem with the main pool right now? It seems to me that it always shows the same information for hours now and it also hasn't found a single block today.
P. S.: Thank you thesnat and tmike for stepping up and doing great work which cannot be appreciated enough! Reading through the last couple of days of this thread really brings up hope again for this coin. God bless your community work and the work of all the devs!
|
|
|
|
|
Show Posts
