So another question regarding the masternodes: My MN is now running for more than 20 hours. The average payout time is roundabout 8 hours, however I haven't received a single payment yet. It still shows "enabled" in my controller (Windows) wallet and "status 4: successfully started" in the MN wallet. How come I haven't received anything yet?
Here is our install guide - https://github.com/carebitcoin/carebitcoin/blob/master/doc/masternode-install.mdplease join our discord/TG for instant support. Ah thank you very much, that one actually looks more recent. Anyway, after 24 hours the payments started to flow and currently I receive a payment every 8-9 hours. So I guess I'll just leave it running, if there are any more problems maybe I will build the MN again from this newer script. Thanks and good luck to your coin and your project.  |
|
|
|
|
So another question regarding the masternodes: My MN is now running for more than 20 hours. The average payout time is roundabout 8 hours, however I haven't received a single payment yet. It still shows "enabled" in my controller (Windows) wallet and "status 4: successfully started" in the MN wallet. How come I haven't received anything yet?
|
|
|
|
Explanations, right. What should we look into Dave? So when you clicked on the PDF, are you saying that its actually not really paid?
Are you saying that accountability.biblepay.org contains fake records? I explained hundreds of pages back that people like Mike have called to see if the payments were made and they were made.
So lets see, that leaves the income side. Are you saying the revenue record is fake? Doesnt it match the average current price?
I'm God Fearing, and there won't be one dollar shorting God's children if I handle a transfer/liquidation and my record shows it. Jaap handles Cameroon, I handle compassion, Andrew handles Kairos, April handles BLOOM, in a decentralized way we have split up the burden across many people.
I'm deliberately going to handle this inquiry another way. Stick to the revenue and expense records on accountability.biblepay.org and post any legitimate question here. Your pasting of illegitimate sanctuaries and transfers is redicules, and quite insulting.
As I explained before: the expense PDFs from last months (May through August) for Compassion only contain endless lists of "total amount due" and "to be billed today", which certainly doesn't look like a receipt but rather like an invoice (in contrast to those up to April). I'm not saying that these payments weren't made, it's just that this doesn't really qualify for an "accountability record" and most certainly doesn't help building any trust from investors. As for the revenue, I never said anything about these records and to be honest I never really looked at them because this should be quite easy to supervise through block explorers and coin price history... On another note: Our coin is now at an all-time-low and I'm pretty sure this is NOT just because no-one knows BBP or wants to invest in it. (Right now no one wants to buy ANY coin really.) The problem rather seems to be that while many (or most of the) other coins are currently just being "hodled", our coin is by design destined to constantly being dumped because of the recurring expenses in FIAT money. Let me ask a simple question: if Compassion has some kind of insurance for sponsored children, why are you so desperate to pay bills right now? (Even thinking of dumping a lot of those children at the expense of others?) Wouldn't it make much more sense to vote YES for the WHOLE Compassion fund, but then NOT exchanging the coins but rather collecting them in an " Orphan Fund", maybe even starting some sancs with it, and selling them in the next bull market? This way no sponsorship would have to be determined, the childen's coins would actually grow over time, and the coin price would have a chance to "breath again". |
|
|
|
Hello all! Unfortunately I didn't find the time to read the WhitePaper yet, however I think this project sounds fantastic and I bought some coins to start a masternode. I tried following the only script I found ( https://github.com/Visco33/Carebit), however this is quite outdated. Several problems occured and I'm not sure I configured it correctly now. 1. The script says 30k coins, but a MN actually is at 120k coins now. 2. The script didn't run through completely, giving errors about the RPC functionality. After manually adding some random rpcpassword in the config this seemed to fix it. 3. The screenshots in the manual show a "create" button in the wallet masternode tab, however there is no such button (win-wallet 3.0.0). 4. I manually edited the masternode.conf, but at first it threw an error that the mn port has to bei 9192 (although the script configures everything on 9191...). 5. The script seems to have installed the MN with a random RPC-pw, but didn't give this at the final output, so now I cannot access the carebitcoin-cli to read out the mn status. 6. My windows wallet actually says "enabled" (albeit with "active: 00h00m") for my mn, although it apparently runs on the "wrong" port number? So to conclude all this: Is there an updated version of the mn install script (or the manual itself)? How do I check if my MN is actually running and how often should there be a payment (roundabout)? Thanks in advance! Edit: I found one of the major problems with this script: it HAS to be run as root (as the user, not as sudo!), otherwise it totally screws up everything by configuring some things as user root and somethings just elevated... I think I got it running now (also correcting the fact that the above script is loading an old version (2.0)), but masternode status says ""code":-1,"message":"Masternode not found in the list of available masternodes. Current status: Node just started, not yet activated". Also, CPU usage of the carebit-daemon is at 100%. This can't be normal... Edit2: Yeah, after multiple restarts and installs it finally synced and is now showing "enabled" as well as the correct MN status. |
|
|
|
|
Thanks jaap for keeping a cool head. Your explanation with the liquidation and recreation indeed makes a lot of sense and I hope that really is all there is to it. Everything else has already been said.
P.S.: I totally agree with your view on "marketing". As a scientist I also despise all that bs, but unfortunately nowadays it seems to be more important than ever, because people usually have the attention span of a 2-year-old kid and (especially in the US) have to be caught by catchy catchphrases, totally exaggerated bla-bla bs and shiny colors and bling-bling ...
|
|
|
|
|
Wow, that's a nice find, Slavino. I think some explanations are in order.
I checked the "accountability" page and this also looks really strange. The last legit invoice from Compassion seems to be from April 22nd (complete print-out of the checkout page). All the newer ones are just plain text BS-PDFs with no signature, no invoice number, not even a slight hint that any money was actually paid (it only says "total amount due"). For Bloom there isn't even a single PDF; Kairo looks legit but of course this is only a very minor payment.
So where did all the proposal payments go to? Can we have some actual payment proof from May 2018 on until August 2018? Deleting all these posts won't help, since they are saved externally.
P.S.: At the slovak guys: Cursing and foul-mouthing doesn't help either; especially not the children...
|
|
|
|
Hello everyone. I discovered this coin just yesterday and have a question: I started mining and the pool already sent a payout to my address (txid ed803289150540efb7ddd233ab8c24a9ee2ab91f11cc9ba3d9d18f96524fb8e4). My wallet (Windows GUI wallet 18.06.2) says it is fully synchronized, but the balance is still 0. I'm not sure what is going on, I never had this issue with any other cryptonight coin. Is there maybe a remote node I could use for the wallet? The "rescan balance" doesn't help either.  Another question would be: my primary address in the wallet starts with Lo.... (which is also the one I mined to), but every new address I create starts with M5... and is NOT accepted by mining pools. What's going on there? EDIT: I (just for the fun of it) changed the "wallet creation block" and somehow my balance shows up, but not the transaction history. Is there any update planned for the wallet? The current one seems to be full of bugs. |
|
|
|
All valid exchange requests were successfully processed.
Coins sent. Check your balance sheets.
Thank you, the transfer came in a couple of hours ago. |
|
|
|
|
Hello everyone.
What is the expected waiting time for the transferred coins to arrive in the new wallet? I sent some FNO yesterday but still did not receive them. Am I right in assuming that this is a completely manual task (not automated at all)?
Thanks!
|
|
|
|
Cannot say anything about Ubuntu 18 (yet), but on my ARMs this version doesn't run stable. After a standard update I randomly got this strange error: sh: 1: ./biblepayd: not found After complete cleanup and reinstalling this didn't occur, but another (familiar) error keeps popping up: *** Error in `biblepayd': double free or corruption (fasttop): 0x0000007f500018b0 *** I'll try and upgrade on of my Pi3s to Ubuntu 18 and see how it goes. |
|
|
|
Does anyone experience this bug in which the wallet periodically becomes unlocked and has to be relocked manually?
Running on Windows 1.1.3.8c.
I've noticed it twice now in the last few weeks.
I have a tiny bit of info on this, so I lean towards this not being a bug. We only unlock your wallet with the crypted passphrase if we receive a boolean "unlocked" state from the wallet on boot. Then we re-lock it if it was "locked" to begin with. So I believe what is happening is at one point you must have typed 'walletpassphrase phrase 99999' or something, and that left the wallet unlocked. Then you restarted the wallet and entered the passphrase. So we unlocked it, tested it, and left it unlocked. To verify the code is working properly, lock the wallet, close the wallet, start the wallet, enter the passphrase and it should still be in the locked state. It will only unlock during PODC updates. I am unable to reproduce this as a bug. I just discovered that my wallet (Windows 10 GUI) was unlocked again. Some days before I locked it and I had it closed tonight. I started it today in the morning and entered the passphrase in the prompt. I'm pretty sure it stayed locked after that. Now in the evening it must have somehow become unlocked again. Cannot find anything in the log.. |
|
|
|
Does anyone experience this bug in which the wallet periodically becomes unlocked and has to be relocked manually?
Running on Windows 1.1.3.8c.
I've noticed it twice now in the last few weeks.
Yes, I've seen that too. Pretty sure it's related to the PODCupdate auto-unlock, haven't found a way to prevent it... |
|
|
|
Nice work guys, really appreciate the efforts! It's always good to get a little compensation for computation.  |
|
|
|
Anyone have trouble installing Ubuntu with GUI on HP Proliants G6's? Upon boot I get a frozen purple screen. Only Ubuntu headless seems to work...Tried nomodeset but didn't seem to work
I also have a G6 and if I remember correctly I had at one point also installed Ubuntu with GUI (16.04 LTS). Never heard of this problem before (but I haven't used GUI Ubuntu for a long time now...). Do you NEED the GUI? If so, you could try installing it afterwards (from the headless version) by apt install unity (or ubuntu-unity-desktop or something like that). BTW: you can always switch between GUI and headless via sudo systemctl set-default multi-user.target
sudo systemctl set-default graphical.target (but then even in the headless version you of course have all the "crap" from the GUI environment^^. |
|
|
|
I have started mining some CRP and it works really well. Also transactions are super fast. I have a question regarding the miner. I started mining under windows and used the binary of the "CPUminer opt - yespower". As soon as I start this, it correctly gives: CPU features: SSE2 AES SSE4.2 AVX AVX2.
SW features: SSE2 AES SSE4.2.
Algo features: SSE2 SHA.
Start mining with SSE2. Now I also have some Linux machines with Dual Xeon CPUs and I compiled the exact same miner on there. Compilation went fine without any problems. However, when I start the miner on Linux (doesn't matter if built on Ubuntu 16 or 18) it gives: CPU features: SSE2 AES SSE4.2.
SW features: SSE2 AES SSE4.2.
Algo features: None.
Start mining with no optimizations.
Also in the source code of the miner there seems to be no optimization file for the yespower algo. It doesn't seem to run unusally slow under Ubuntu. I get approx. 1 kH/s for a dual Xeon L5640, but it just seems strange to me... |
|
|
|
Hi all. I have 2 small questions: 1. Apparently IBM finally came to terms regarding the WCG stats ( https://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,40876_offset,130). Are there any plans yet to resume the Byte distribution for WCG? 2. I had a bet placed on the football world championship semi-final. Now for more than 2 days I cannot redeem the winning contract. As soon as I hit "send" it doesn't really do anything but wait and sometimes synchronize and eventually gives "[internal] response timeout". Is this also related to the extremely slow network at the moment or is there an additional problem with the betting bot? |
|
|
|
Don't know if someone posted already, but since it was brought up again: Kucoin currently has a free-listing-vote-competition running right now. Only problem is that you have to be signed on the exchange and join the Telegram group. Apparently you can propose any project, but you should write in short times why it would deserve to be listed there. https://medium.com/kucoinexchange/vote-for-your-coin-telegram-action-f749362be26a |
|
|
|
I like the background prayer load feature also. The reason it was disabled is TheSnat had a couple instances of a 5+ minute loading time, and I got very nervous that we had a race condition so I disabled it. You have to realize the feature is not just for prayers but also for PODC data, so its critical the wallet has it all in order before the chain finishes syncing... So we will have to revisit this again and ensure there is really no race. There is a pull we need from thesnat for the transaction list which confuses the issue (as the extra-long load started at the same time we added tx list filtering And background prayers), so we need to insert one fix at a time and verify it.
Ah I see. Well, in that case of course it's better save than sorry. The mandatory seems to have gone through without problems and the pools are finding blocks. Good job everyone! @Lichtsucher: On purepool I have some "JSONRPCException" errors on my workers. Never seen those before. Could they be related to the wrong balance (0.00 BBP) showing? Edit: So the span between PODC payouts is 215 block now, correct? Are there some adjustments to the (targeted) block time? Otherwise it would be even more than the previous ~25 hours between the superblocks? |
|
|
|
Thank you very much. This saved me hours, if not days of syncing. Don't know where the problem was, but I was stuck in "12 weeks remaining" since yesterday. With your files I was "9 hours behind" and the sync took not even 20 seconds to finish. |
|
|
|
I am just checking the machine leadboard and find something interesting:
manasd 27315.81 7/9/2018 6:06:42 AM 3391974 89828.89 GenuineIntel Intel(R) Celeron(R) CPU G1620 @ 2.70GHz [Family 6 Model 58 Stepping 9] 1994560 2 8151.14 MB 3282.09 0.8 27.31581 1.312836
For this slow machine with 2 core, how could he achieve such a high RAC? Is there any trick we do not know?
GPU for rosetta?
[6] AMD AMD Radeon (TM) R9 380 Series (4096MB) OpenCL: 2.0 It would appear that way. edit: seems they abandoned the project https://biblepay-central.org/en/podc/user/1994560/I was wondering that quite some time ago, there were others too where the RAC didn't add up to the seemingly slow hardware. The solution however is quite simple: Rosetta (or BOINC) reads the hardware from system files. If you know where to look for it should be quite easy (especially under Linux) to edit those and write in any hardware you want. If then you copy-paste images of your whole installed operating system to your other machines it appears as if you have dozens of weak CPUs crunching a lot of RAC. However, why you would go through all that trouble is beyond me... on another note: Why was the wallet feature "memorize prayers AFTER wallet start" abandoned? I really liked that I didn't have to wait several minutes until the wallet was opened. |
|
|
|
|
Show Posts
