|
Is there a possibility that a botnet could be gaming the system and e.g. mine in the future so that it finds all the blocks? Someone is finding all the blocks it would just be interesting to know who it is and how they are doing it.
|
|
|
|
|
It looks to me like the dev might have made his money and moved on.
|
|
|
|
|
I wonder if the botnets will join the pool or if they will keep on solo mining.
|
|
|
|
Guys (and Girls), I just deployed the Prod pool and enabled it for prod testing.
The settings are all the same as testnet, so you should now be able to reboot and start testing against prod.
The payment system is turned on (knock on wood) against the prod server for BBP also.
I see a few miners are already hitting it- if you would, please restart your nodes, as Id like to clear out any old mining threads.
What must be changed to mine prod pool instead of testnet pool? Also which version of the wallet is required? Yes, but the mining info in the wallet says it is pool mining on mainnet but the pool does not display my miner. It does not seem to pick it up. |
|
|
|
Guys (and Girls), I just deployed the Prod pool and enabled it for prod testing.
The settings are all the same as testnet, so you should now be able to reboot and start testing against prod.
The payment system is turned on (knock on wood) against the prod server for BBP also.
I see a few miners are already hitting it- if you would, please restart your nodes, as Id like to clear out any old mining threads.
What must be changed to mine prod pool instead of testnet pool? Also which version of the wallet is required? |
|
|
|
|
Does the new wallet solve the issue where blocks are found but it throws an error?
|
|
|
|
|
Withdrawal and anonymous works fine. Hash rate is close enough.
|
|
|
|
|
Dev Can you explain the reasoning behind the size of the block reward and the effect on inflation.
|
|
|
|
ok am i doing something wrong. I had been mining for about 5 days on an older laptop and had not found anything so i figured ok, maybe its because its older it does not have the power to do this. So 2 days ago i used some free credits to spin up a could server to do nothing but hash biblepay. 2 days and still nothing. Here is my info
15:01:10

getmininginfo
15:01:10

{
"blocks": 2543,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 0.02009845991238194,
"errors": "",
"genproclimit": 15,
"network_khashps": 8197.110849637433,
"hashps": 129345.4001071014,
"minerstarttime": "08-09-2017 19:41:18",
"pooledtx": 0,
"testnet": false,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolmining": false
}
What am i doing wrong or am i just that unlucky.
You are not doing anything wrong. Iv ran 600k for a day without any blocks and found 2 just as I was going to shut it down. I am letting it run a little while longer. Hopefully the pool will be up soon. |
|
|
|
Im having trouble with linux as well (Ubuntu 16.04) ==== References: https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt https://michael.mckinnon.id.au/2016/05/13/building-a-namecoin-server-with-ubuntu-16-04/https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md==== Step by Step Commands (not sure if this is all correct, please someone point out any issues) sudo apt-get install g++ sudo apt install make sudo apt-get install build-essential sudo apt-get install autoconf libtool pkg-config sudo apt-get install libboost-all-dev libssl-dev libevent-dev sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler cd /home/yourname git clone https://github.com/biblepay/biblepayBP_ROOT=$(pwd) BDB_PREFIX="${BP_ROOT}/db4" mkdir -p $BDB_PREFIX wget ' http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz' echo '12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef db-4.8.30.NC.tar.gz' | sha256sum -c tar -xzvf db-4.8.30.NC.tar.gz cd db-4.8.30.NC/build_unix ../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX make install cd $BP_ROOT ./autogen.sh ./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/" sudo make =================== And then it freezes on last command sudo make, last output: CXX libbitcoin_server_a-init.o Ive been waiting 20 minutes, is it frozen?, did I do something wrong? or do I need to wait longer? (Its just a one core machine Im testing/building on, I have very little Linux experience and almost no mining experience) The very first compile takes over an hour on a fast machine as it has to build all the obj files and moc stuff for qt. Wow, one hour is really lol... i never built a wallet with more than 30 minutes before. But I will try with togoshigekata method in my Ubuntu 16.04 later. Will update my status. Okay, I managed to build the wallet successfully. But it is not the gui version, or maybe I overlook it? How to build for the qt GUI wallet? If all your qt dependencies are there then look in biblepay/src/qt for the qt binary. |
|
|
|
Well, that would be why it's wasn't credited. It's pretty unusual, I don't think I've solo mined any orphan Biblepay blocks. Does getmininginfo show that you're on block 2488 right now? As far as the address goes, that's normal. A new receiving address is generated whenever you receive a block reward. It all ends up in your wallet. So the wallet displays an incoming transaction popup for transactions that aren't actually being credited? That's pretty absurd... Really discouraging to be informed that I've mined a block when that's not actually true. As a user, I don't want to be told about non-existent incoming transactions. Don't tease me, confuse me, and waste my time! Sheesh. This is perfectly normal and happens in all coins. An orphan is a block that you solved and submitted to the network but someone else also solved a block at almost the same time and also submitted. Due to various reasons including latency the network receives and accepts the other miner's block and rejects yours. The block you solved then becomes an orphan. This is most prevelant when a coin launches and lots of blocks are solved in quick succession at low difficulty, but it can happen at any time. Before you blame it on the dev, rather do things from your side like increase your internet speed but most of all your latency. Go fixed line or fibre or even better, mine in the cloud where the internet is super fast. |
|
|
|
|
Shutting down my my miners. Did not find one block with 600k hashes for a whole day.
|
|
|
|
|
Some feedback:
1. When you click on switch to testnet it toggles to switch to mainnet. When you click on another like like home, the link switch to mainnet defaults back to switch to testnet which is not correct.
2. There is no page to see stats on the blocks found, who found them, when found, the block's status etc.
3. No anonymous mining option.
4. Pool hash indicator is very close to client side hash
|
|
|
|
Optimized. The latest wallet works much better.  How many processors and cores does the box have? About 4 and 8? 16 cores |
|
|
|
Optimized. The latest wallet works much better. |
|
|
|
Thanks my goal was to build from source, i already run the binaries, but i would rather build my own. Call my paranoid!  Now the cli is building but im stuck at an error while building the daemon: CXXLD biblepayd.exe libbitcoin_zmq.a(libbitcoin_zmq_a-zmqnotificationinterface.o):zmqnotificationinterface.cpp:(.text+0x47d): undefined reference to `__imp_zmq_ctx_destroy' libbitcoin_zmq.a(libbitcoin_zmq_a-zmqnotificationinterface.o):zmqnotificationinterface.cpp:(.text+0x6a6): undefined reference to `__imp_zmq_strerror' and a couple more undefined ref about the zmq implementation... Im close... Ok then try sudo apt-get install libzmq3-dev |
|
|
|
Ive been able to compile the bitcoin wallet, but no luck with biblepay. I did went closer by copying the depends folder from bitcoin to biblepay, seems like you're missing a Makefile in there.
But the error i have now is farther and it's errors like this one:
.libs/libbitcoinconsensus_la-utilstrencodings.o:(.data.DW.ref.__gxx_personality_v0[DW.ref.__gxx_personality_v0]+0x0): undefined reference to `__gxx_personality_v0'
it seems to be related to the libstdc++ library.
Which i have run a few apt-get to make sure it was installed...
If you are still struggling, you can try these compiled versions for Ubuntu 16.04 (at your own risk of course). You might still be missing a dependency though on your side. Ill look into posting a full list of dependencies I used to compile shortly. biblepay-cli v1.0.1.7 Download linkVirustotal linksha256 hash 148e93975996a987e7b8bc90f74d9ffe290e74ebd043faee0af85caede964fcd biblepayd v1.0.1.7 Download link Virustotal link sha256 hash b9fb4a5705dfb777464d1069169aa7b7f3c75d675afcc3bb5cb68be2780a13ef biblepay-tx v1.0.1.7 Download linkVirustotal linksha256 hash 17c6cfbce648d72b32a6e16aab09f970c6030665ca5bc6f1739842d6dca19aa5 biblepay-qt v1.0.1.7 Download linkVirustotal linksha256 hash 5b2ce146875e8328ab2d1186e91a65268e3214f65628354707e8dd16b3cbe6ce |
|
|
|
Hi guys,
So i downloaded the Wallet Let it sync then opened the debug console and typed in 'setgenerate true 2' and the the next line was 'getgenerate' which returned true.
Also i sent a 'getmininginfo' and got the following
{
"blocks": 1991,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 0.00580225551959311,
"errors": "",
"genproclimit": 2,
"network_khashps": 2813.731059902567,
"hashps": 3904.196392532182,
"minerstarttime": 1502042033559,
"pooledtx": 0,
"testnet": false,
"chain": "main",
"biblepay-generate": true
}
And then a 'getinfo' and got this
{
"version": 1000107,
"protocolversion": 70707,
"walletversion": 61000,
"wallet_fullversion": "1.0.1.7",
"balance": 0.00000000,
"privatesend_balance": 0.00000000,
"blocks": 1991,
"timeoffset": 0,
"connections": 3,
"proxy": "",
"difficulty": 0.000580225551959311,
"testnet": false,
"keypoololdest": 1502026134,
"keypoolsize": 1008,
"paytxfee": 0.00000000,
"relayfee": 0.00010000,
"errors": ""
}
So the miner has been on for about 3 hours straight and i have 0 bbp.
What is the matter?
I also opened the conf file on notepad and it was blank and i inserted the following piece of code
gen=1
genproclimit=10
addnode=node.biblepay.org:40000
Still have no response...
I run an i5 6th generation on my HP laptop.
Can someone help me out please?
I have 2 outgoing connections and 0 incoming.
I also have 0 masternodes.
Please help me out here.
I can see @bible_pay being active here...
Quite happy to see a Dev work it out.
If someone would help.. I would be really happy.
Thanks in Advance,
Akaash
1) Download hwmonitor from cpuid and run it next to your wallet. 2) Remove the genproclimit from your .conf 3) A couple pages back is a list of nodes. Add that list into your .conf 4) In your debug console, type "setgenerate true x". Replace x with the number of threads you want. Start at 4 and up them in 5s or 10s and see the effect on your cpu usage in hwmonitor. As soon as you reach 98-100% on all cores, you stick to that number of threads. 5) Type "getmininginfo" everytime after a thread change and see where your hashes are optimized. |
|
|
|
|
What do you think a reasonable amount would be for a sanctuary - 1m?
PS: Anyone selling? Send me a PM.
|
|
|
|
Hi friends,
maybe somebody can help me with a problem?!
Situation:
- I downloaded a Stratis wallet for myself onto my laptop (later named laptop 1) and transferred some Stratis to the wallet
- then I downloaded an other Stratis wallet for my girlfriend on her laptop (later named laptop 2) and transferred some Stratis to the wallet
For both Wallets we used the same seed and I saved the backups for both.
Now, while travelling Laptop 1 got stolen so that we both have to use Laptop 2.
Is it possible to run both Wallets on the same laptop?
If yes: How??
Many thanks in advance & kind regards
Option 1 - single installation with multiple wallets: If you have both wallet.dat files and you want to access the coins from a single wallet you can use both. Rename the laptop 1 file wallet.dat.1 and the second wallet.dat.2. The one that you want to use, close the wallet and rename the file to wallet.dat. Afterwards rename it back to 1 or 2. Option 2 - single installation with one wallet: If you have the private keys import the private keys of the wallet from the stolen laptop to the wallet on the other laptop and both wallets will be combined into one. Option 3 - multiple installations: Create a folder roaming\stratis2. Copy all the files from the main roaming\stratis folder to the new folder except the wallet.dat file. Cooy the backup wallet.dat file from the stolen notebook to the roaming\stratis2 folder. In your stratis.conf file in the stratis2 folder add the lines port=10000 and rpcport=10001. Create a desktop icon called Stratis2 and in the path let it open "stratis-qt -datadir=c:\users\yourusername\appdata\roaming\stratis2". When you click on this icon it will open the second wallet. Running just "stratis-qt" will open the first wallet. |
|
|
|
|
Show Posts
