James was able to rewrite the internal communication of SuperNET this weekend to make it easier for Windows to handle. With this simple 32 bit clipping bug fixed, my work porting SuperNET to Windows is drawing to a close, as it is now working. I will update the build instructions soon and post them in slack so supernet will be running inside BTCD. Once I get the nonbundled agents working I hope to release another demo video showing how we can query InstantDEX directly from BitcoinDark debug window and run the awesome html gui alongside btcd and Nxt. Things are really getting close.  Matthew |
|
|
|
Will the same automatic .config creation be happening with the Mac download, too?
Yes, once someone compiles it. I don't have a Mac. |
|
|
|
Hi All, I took a break from debugging SuperNET-enabled BitcoinDark for Windows today to update the vanilla BTCD release with automatic BitcoinDark.conf generation. WHAT THIS MEANS If you don't know what a .conf file is, don't worry about it! Just download and unzip the executable, and run it. It will find peers quickly. If you do know, it will check for BitcoinDark.conf on launch. If it finds it, it skips it. If it doesn't, it will create a 5 character random username and 15 character random password and generate a BitcoinDark.conf file with a list of nodes. I plan to update these nodes from time to time. Azeh will update the official Bitbucket download soon, but for now I have uploaded it at: https://mega.co.nz/#!U0d1QShC!W2RllvIRWPBYbMNbd0mgoo9LZRPfaI_gv7AwCGUCo3gmatthew@matthew:~/Desktop$ sha1sum BitcoinDark-qt.rar
d6a48339b413660334cb5442c8f8259469a7dc5c BitcoinDark-qt.rar
Source at github.com/laowais/bitcoindarkMatthew |
|
|
|
where are all the btcd? almost no sell orders on exchanges. James is controlling way too many BTCD. Very unhealthy for a "currency". Maybe the tech is pioneering but as long as one person is controlling 20-40% i will not buy into it.
Perhaps you don't remember James posting "WTB BTCD" all over the place last year. He purchased every BitcoinDark on his dime, on the open market. We have disclosed the exact figures on the premine, it's a drop in the bucket compared to many BTCD stackers. |
|
|
|
|
Great dividend this week.
Hope to staking continue to rise.
Matthew
|
|
|
|
Boost
-----
DOS prompt:
downloaded boost jam 3.1.18
cd \boost-1.47.0-mgw
bjam toolset=gcc --build-type=complete stage
it shows:
c:/mingw/bin/../lib/gcc/ming32/4.6.2/../../../../mingw32/bin/ld.exe: cannot find -lboost_thread_win32-mgw46-mt-s-1_54 collect2: ld 1
Those are two different versions of boost. Make sure you put the correct version and prefix (i.e. _win32-mgwxx-mt-whatever) in the makefile. Matthew |
|
|
|
BTCD wallet released in mid-2014 with zero upgrades since...
Except for the BitcoinDark repo with 4,040 commits. |
|
|
|
BitcoinDark Weekly Dividends to Stakers
This week's dividends have been paid to BitcoinDark stakers: 52 BTCD in total.
Including the 1.7 rolled over from last week, 14 BTCD from MM-BTCD
8 from Mivond and bitcoindarkdice.net
30 from Cassius, whom generously donated his blog fee to BTCD Stakers
A warm thanks to the above for their contribution in support of BitcoinDark. Please remember to keep your wallet unlocked for staking in order to receive weekly dividends.
Great dividend week, and we are just getting started  A big thanks to mivond from bitcoindarkdice.net and cassius. |
|
|
|
James (jl777) Cross-Post from Slack:BTCD Lchains MGW is ready for testing. Install BitcoinDarkd:git clone https://github.com/jl777/btcd cd btcd/libjl777 make dependencies; make onetime; make btcd; echo "{\"secret\":\"randvals\",\"userdir\":\"$HOME\"}" > SuperNET.conf; ./BitcoinDarkd then get a deposit address: ./BitcoinDarkd SuperNET '{"plugin":"MGW","method":"msigaddr","coin":"BTCD","userNXT":"NXT-KAK4-SDL7-DHGT-9W37B","broadcastflag":1}' if it is a brand new acct without pubkey: ./BitcoinDarkd SuperNET '{"plugin":"peers","method":"msigaddr","coin":"BTCD","userNXT":"NXT-KAK4-SDL7-DHGT-9W37B","userpubkey":"8e7aeb3f92f5aa9d2c32c3c4fcda55deab8eda958237289b7e3d38959cfbf278","buyNXT":10,"broadcastflag":1}' deposit to the "address":"bRYAfqJwjMKJbt2o2TUAqUZSpnVWhz17xP" that is returned from the "msigaddr" call (takes about 2 seconds) it is set for 10 coin confirms you can test withdraw by doing an asset transfer to the issuer NXT-JXRD-GKMR-WD9Y-83CK7, but make sure to have a NOT encrypted message:{"withdrawaddr":"<btcd addr>"} the JSON cannot have any syntax errors and it needs to be a valid btcd address and the message cannot be encrypted I have ported supernet for Windows, am fixing bugs. Hopefully Windows users will be testing this soon as well |
|
|
|
Is anyone-else experiencing the same phenomenon? - A db file that doesn't update but the wallet nevertheless functioning ok?
I haven't spent much time reading the btc code appending the blockchain file so this is my guess as to what's going on, but I've spent plenty of time reading from the file directly. blk00001.dat is just a file with accepted blocks laid out in sequence. i.e. block0_bits->block1_bits->block2_bits->... You say that you are synced up now. Would you want the blockchain file to append every block it sees? Probably not, especially after what just happened with all the syncing issues. You'd probably choose to let the chain build for a while before appending a block to the file on disk, to eliminate the risk of a block being rejected later. In short, it's probably just waiting for 110 confirms to write the latest blocks to disk. Any advice what to do next?
Hodl for liftoff Matthew |
|
|
|
The wallet is not sync how to do
Hi, Sorry you are having this problem. Try deleting peers.dat from your BitcoinDark folder and restarting BitcoinDark. If that doesn't work, you may have to delete everything in the folder except wallet.dat and BitcoinDark.conf and let it resync. Matthew |
|
|
|
This is the reason I added a strong random password generation to the upcoming BitcoinDark wallet.
Honestly, we ought to just remove rpcuser and rpcpassword fields from the default conf.
rpcuser and rpcpassword allow you access to the BitcoinDark functionality from outside code. If you are just using BTCD-qt as a wallet without ever making some program that uses it remotely, you DO NOT need those fields.
IF you include rpcuser and rpcpassword, give them both unique, random names.
DO NOT EVER use user and pass.
Here is a good example:
rpcuser=fh3hf3hfhf
rpcpassword=m34uvn9u9v424!mvfj4
Basically, if you don't know what RPC is used for, don't include it!
Matthew
So, you are suggesting that those two lines simply be deleted from the suggested code at the beginning of this thread in the OP? Is it true that I don't need those two lines in my .conf? Can I can simply remake my .conf file without them, overwrite my original .conf file and go back to business as usual without making any other changes or needing to reinstall my wallet? Open your BitcoinDark.conf, delete rpcuser and rpcpassword, take out server=1, and save it. Then restart BitcoinDark. |
|
|
|
please don't use this in your config file.
///////////////////////////////////////////////
rpcuser=user
rpcpassword=pass
rpcport=14632
port=14631
daemon=1
gen=1
server=1
//////////////////////////////////////////////
Why? Its from the OP, and working perfectly for me. Because inexperienced user will not change "pass" to their unique password and their system could very possibly get compromised. Guys and Gals, so that I can get all the guides correct for everyone, including for noobs like me (who are actually not so new), can I please get a few specific answers to each question posted below? I will then revise the guides to make them idiot proof. I am a decent technical writer largely because I am still close to being new at this and can explain things well to less experienced people, as long as I understand all the concepts. Here is what I need specific answers for: When you type what you are supposed to type in those rpcuser=user, rpcpassword=pass fields, how do you know what your "user" name is and what your "password" is when you first make the wallet? I am asking because someone brand new at this (and actually me right now) would wonder how they already have a user name and password when they haven't even done anything yet or signed up for anything anywhere. Do you just type random stuff in both fields? If you just type random stuff, do you ever need to access that random stuff or input it later for any reason? Do you need to remember the random stuff you type in those fields or write it down? If you do need to remember it, why do you need to remember it? Is any of what you are supposed to type in those rpcuser=user, rpcpassword=pass fields based on the same password you use to encrypt the wallet? Does there need to be any congruency between the encryption of your wallet and what you type in those fields? Please let me know SPECIFIC answers to those few simple questions, and I will revise the guide to everyone's satisfaction. Also, thank you to GIminer for pointing this all out. It didn't just help noobs... it helped me, because I have been rolling for a long time with exactly that code that I was supposed to change! I had no idea. This is the reason I added a strong random password generation to the upcoming BitcoinDark wallet. Honestly, we ought to just remove rpcuser and rpcpassword fields from the default conf. rpcuser and rpcpassword allow you access to the BitcoinDark functionality from outside code. If you are just using BTCD-qt as a wallet without ever making some program that uses it remotely, you DO NOT need those fields. IF you include rpcuser and rpcpassword, give them both unique, random names. DO NOT EVER use user and pass. Here is a good example: rpcuser=fh3hf3hfhf rpcpassword=m34uvn9u9v424!mvfj4 Basically, if you don't know what RPC is used for, don't include it! Matthew |
|
|
|
Hi,
I have a suggestion, a common mistake amongs the who aren't tech savvy happends is to copy/paste literally the part
rpcuser=user
rpcpassword=pass
of the suggested code to make a conf file. Long time ago I did that mistake when I made my first conf file for another coin's wallet.
I know is too noob, but being quite usual mistake and one that can compromise the wallet's security, I strongly suggest to stress that at the Bitcondark.conf's code at the OP.
As example, something like that:
rpcuser=type your user
rpcpassword=type your password
Thanks
I have already implemented automatic BitcoinDark.conf generation in the upcoming BTCD wallet at github.com/jl777/btcdI generates a strong 12 character random password. |
|
|
|
|
Hi Everyone,
It seems there has been some issue around block 5550559. Yes, it is coming at a bad time since BitcoinDark has been on an accelerating upward trajectory lately.
If you are stuck, the first thing I would do is to delete your peers.dat and restart BitcoinDark. If that doesn't work, try deleting your blockchain and resyncing.
Many people have been fixing this issue by deleting everything except their wallet and BitcoinDark.conf.
In fact, here are some nodes that seem to be synced:
addnode=192.99.203.53
addnode=198.50.152.135
In fact, I myself have restarted my vps's.
When clear consensus is lost, it takes some time to restore the longest chain. That's just the nature of a blockchain.
crackfoo has informed me that he received the daily BTCD payments from the exchanges, so they are on the correct chain.
Thanks,
Matthew
|
|
|
|
|
Good news!
Azeh was able to use the getstakers rpc command and a custom automated dividend payer script I wrote to automatically send out this weeks' MM-BTCD revenue to the past weeks' BitcoinDark stakers!
This is the first time a 'gen1' cryptocurrency has paid dividends! It is an historic day indeed. Remember, InstantDEX, SuperNET, possibly crypto777 and other services will be paying 5% of their revenues directly to staking addresses.
If you missed the payment, make sure to stake as much as you can for next week's dividend!
Matthew
|
|
|
|
so, if now supernet is just a plug in of btcd it is a best choice to buy btcd than supernet
I bought some. Not only you, my friend! Nice rise at bittrex today! It seems that with all the hodling, large miners switching to BTCD output on the multipool, mm-btcd starting to pay dividends in btcd (not to mention the upcoming dividends from other revenue streams) we are putting some positive pressure on the btcd price |
|
|
|
Hi all, I have taken a short break from porting SuperNET to Windows and working with James to develop Ramchains to add a mechanism into BitcoinDark to help automate the dividend process. We have promised 5% of the revenues of various services will go directly to BitcoinDark stakers, including, but not limited to, InstantDEX (5%), SuperNET (5%), and potentially other assets which are in the pipeline. MM-BTCD will also be paying dividends directly to BTCD stakers. Direct dividends to stakers will be done over certain intervals. This means that your percentage of the total dividend is dependent on the number of blocks you stake, not how much BTCD you stake. This has the effect of incentivising constant staking, thus helping to secure the network. How does it work? I added a new RPC call to BitcoinDark, getstakers. This command returns a string of all the addresses which staked blocks between two given intervals. You can access it from the debug console in BitcoinDark-qt. Example: getstakers 100000 100005
{
"Addresses:" : "'{\"RFzJFDXULPvy7y6xfChUUorieYnr2c81HX\"\", \"RDGi3CKdYC7h3cqXFTyd2xPkTVkwza83aw\"\", \"RWE5VQQ6oDKGyXJxWh3FPQ7RFJFiZWDjYN\"\", \"RQKB86ur6gA7xpJW3Eh12az5EJp8WWe3vx\"\", \"RNVdKEDirp4REpMQ1hJGPxKJhfFfDeWzn7\"\", \"RSn23Tv5mR3Y23a9KsW7JHHJCte2exux2H\"\"}'"
}
These addresses staked blocks 100,000, 100,001, 100,002, 100,003, 100,004, and 100,005, respectively. What about the dividends though? Say InstantDEX is up and running and has made 1000BTC. It wants to pay out its 5% share (50BTC) for the month to BitcoinDark stakers. It first calculates the block interval which represents that month. Just to keep things short I'll only make the interval a few blocks long: getstakers 500000 500005 50
{
"Addresses:" : "'{\"RCs9Sqe99sRDD3yKCfY39VvShamcGXXSRD\"\": 8.33333, \"RX8ziTPuKqfxJemHdrFcCEpJKpbDFgXwNn\"\": 8.33333, \"RTopxEU3vZsu81KdRUdMfP2QR31kbwCGeP\"\": 8.33333, \"RRYbXEkZokCns4EQfpTB6DnEyMF98cVFVQ\"\": 8.33333, \"RYEZ1VdiFxLthKKLZzU5iDHNfgX4EiCVNc\"\": 8.33333, \"RLM1DaCS9kJ9e7EcyHHXiuw9DsgdEFxU12\"\": 8.33333}'"
}
You simply pass the total amount to be paid out and it automatically calculates how much each address should get. It also puts it in a form for another, standard, RPC call, sendmany: sendmany "" '{"RCs9Sqe99sRDD3yKCfY39VvShamcGXXSRD": 8.33333, "RX8ziTPuKqfxJemHdrFcCEpJKpbDFgXwNn": 8.33333, "RTopxEU3vZsu81KdRUdMfP2QR31kbwCGeP": 8.33333, "RRYbXEkZokCns4EQfpTB6DnEyMF98cVFVQ": 8.33333, "RYEZ1VdiFxLthKKLZzU5iDHNfgX4EiCVNc": 8.33333, "RLM1DaCS9kJ9e7EcyHHXiuw9DsgdEFxU12": 8.33333}'Run the above command and the dividend will be sent out to all stakers for the appropriate time interval. That's it! I have updated the vanilla BTCD repo ( https://github.com/laowais/bitcoindark) with this functionality, so you may build it yourself or download the binary here: https://mega.co.nz/#!sss3kRTJ!IdofVJVllG0jzNIFa3cHdC6hUArM3A7lGg4NHhZkuecSHA-1 Hash: 069320d2688d8a5e8a8c899ac9e2063ca4ef703a I expect this link will replace the OP link soon. We are making really great progress with this project. Ramchains are performing really well, as is InstantDEX, and I am close to porting the updated plugin-based SuperNET to Windows. Once this first batch of tech. makes it through testing, release, etc. we will resume work on teleport and all the other great features for which you are waiting so patiently. Believe me, I am just as excited as you are! If you haven't joined slack, please do! We have hundreds of people there and we lost 0 time due to BitcoinTalk troubles. SuperNET is now a plug-in of BitcoinDark. Matthew |
|
|
|
Hi all, I have taken a short break from porting SuperNET to Windows and working with James to develop Ramchains to add a mechanism into BitcoinDark to help automate the dividend process. We have promised 5% of the revenues of various services will go directly to BitcoinDark stakers, including, but not limited to, InstantDEX (5%), SuperNET (5%), and potentially other assets which are in the pipeline. MM-BTCD will also be paying dividends directly to BTCD stakers. Direct dividends to stakers will be done over certain intervals. This means that your percentage of the total dividend is dependent on the number of blocks you stake, not how much BTCD you stake. This has the effect of incentivising constant staking, thus helping to secure the network. How does it work? I added a new RPC call to BitcoinDark, getstakers. This command returns a string of all the addresses which staked blocks between two given intervals. You can access it from the debug console in BitcoinDark-qt. Example: getstakers 100000 100005
{
"Addresses:" : "'{\"RFzJFDXULPvy7y6xfChUUorieYnr2c81HX\"\", \"RDGi3CKdYC7h3cqXFTyd2xPkTVkwza83aw\"\", \"RWE5VQQ6oDKGyXJxWh3FPQ7RFJFiZWDjYN\"\", \"RQKB86ur6gA7xpJW3Eh12az5EJp8WWe3vx\"\", \"RNVdKEDirp4REpMQ1hJGPxKJhfFfDeWzn7\"\", \"RSn23Tv5mR3Y23a9KsW7JHHJCte2exux2H\"\"}'"
}
These addresses staked blocks 100,000, 100,001, 100,002, 100,003, 100,004, and 100,005, respectively. What about the dividends though? Say InstantDEX is up and running and has made 1000BTC. It wants to pay out its 5% share (50BTC) for the month to BitcoinDark stakers. It first calculates the block interval which represents that month. Just to keep things short I'll only make the interval a few blocks long: getstakers 500000 500005 50
{
"Addresses:" : "'{\"RCs9Sqe99sRDD3yKCfY39VvShamcGXXSRD\"\": 8.33333, \"RX8ziTPuKqfxJemHdrFcCEpJKpbDFgXwNn\"\": 8.33333, \"RTopxEU3vZsu81KdRUdMfP2QR31kbwCGeP\"\": 8.33333, \"RRYbXEkZokCns4EQfpTB6DnEyMF98cVFVQ\"\": 8.33333, \"RYEZ1VdiFxLthKKLZzU5iDHNfgX4EiCVNc\"\": 8.33333, \"RLM1DaCS9kJ9e7EcyHHXiuw9DsgdEFxU12\"\": 8.33333}'"
}
You simply pass the total amount to be paid out and it automatically calculates how much each address should get. It also puts it in a form for another, standard, RPC call, sendmany: sendmany "" '{"RCs9Sqe99sRDD3yKCfY39VvShamcGXXSRD": 8.33333, "RX8ziTPuKqfxJemHdrFcCEpJKpbDFgXwNn": 8.33333, "RTopxEU3vZsu81KdRUdMfP2QR31kbwCGeP": 8.33333, "RRYbXEkZokCns4EQfpTB6DnEyMF98cVFVQ": 8.33333, "RYEZ1VdiFxLthKKLZzU5iDHNfgX4EiCVNc": 8.33333, "RLM1DaCS9kJ9e7EcyHHXiuw9DsgdEFxU12": 8.33333}'Run the above command and the dividend will be sent out to all stakers for the appropriate time interval. That's it! I have updated the vanilla BTCD repo ( https://github.com/laowais/bitcoindark) with this functionality, so you may build it yourself or download the binary here: https://mega.co.nz/#!sss3kRTJ!IdofVJVllG0jzNIFa3cHdC6hUArM3A7lGg4NHhZkuecSHA-1 Hash: 069320d2688d8a5e8a8c899ac9e2063ca4ef703a I expect this link will replace the OP link soon. We are making really great progress with this project. Ramchains are performing really well, as is InstantDEX, and I am close to porting the updated plugin-based SuperNET to Windows. Once this first batch of tech. makes it through testing, release, etc. we will resume work on teleport and all the other great features for which you are waiting so patiently. Believe me, I am just as excited as you are! If you haven't joined slack, please do! We have hundreds of people there and we lost 0 time due to BitcoinTalk troubles. SuperNET is now a plug-in of BitcoinDark. Matthew |
|
|
|
|
Show Posts
