Your Bitcoin transactions The Ultimate Bitcoin mixer made truly anonymous. with an advanced technology. Mix coins



Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.

thefrog



Offline



Activity: 393

Merit: 250







Sr. MemberActivity: 393Merit: 250 Re: ★★ DigiByte ★★ [DGB] ✈ ✔ MultiAlgo v3.0.1 officially released! Mandatory Update! August 19, 2014, 10:54:48 PM #10910 Quote from: allcrypt on August 19, 2014, 10:48:16 PM Starting the new digibyte with an EMPTY (except for a digibyte.conf file) directory gives us:



: Error initializing wallet database environment [removed for security].digibyte!



Yes the directory exists. Yes there is a readable digibyte.conf file.



But it wont start.



If anyone has a solution please send a PM or support ticket on allcrypt.com





can you do a ldd on the digibyted daemon binary ?

and a 'file' on the same binary ?



I had a similar issue if I remember correctly either with trying to run 64bit binary in a 32bit OS (debian both), or I had this when I compiled with libdb5.1 but had old libdb4.8 around and digibyted tried to use that one.

Can't remember which case it was, I think it was the second one. can you do a ldd on the digibyted daemon binary ?and a 'file' on the same binary ?I had a similar issue if I remember correctly either with trying to run 64bit binary in a 32bit OS (debian both), or I had this when I compiled with libdb5.1 but had old libdb4.8 around and digibyted tried to use that one.Can't remember which case it was, I think it was the second one.

birdonwheels5



Offline



Activity: 160

Merit: 100







Full MemberActivity: 160Merit: 100 Re: ★★ DigiByte ★★ [DGB] ✈ ✔ MultiAlgo v3.0.1 officially released! Mandatory Update! August 20, 2014, 12:56:59 AM

Last edit: August 20, 2014, 04:19:01 AM by birdonwheels5 #10914



The p2pools throw an "out of memory" error if you try launching them, but I believe that's because there is currently no work available from the new algorithms. MAKE ABSOLUTELY SURE that you set the correct algorithm in the digibyte.conf file, stop the daemon and restart it after saving. Blocks found under the wrong algorithm will NOT BE ACCEPTED by the network! (Ex your daemon is sending work out for qubit and you're hashing with sha256).



I'll be releasing the source at the bottom of this post, but I would appreciate if you guys would mine on my nodes (I spent quite a few hours preparing the code & the nodes, and I'm setting the fee to a low 0.5%) to support me and my work. Donations would also be appreciated If there are any bugs, please open an issue on the github repo (wasn't able to thoroughly test due to no testnet being up), and if you would like your node added as a bootstrap, please submit a pull request in the github repo with your node's address added as a bootstrap.



Also, my nodes are located in the USA, on the east coast near Boston.





Links to my nodes (They are down right now, but will be live once Multi-algo goes live):



SHA256:



Groestl:



Skein:



Qubit:





Links to the source code:



SHA256:



Groestl:



Skein:



Qubit:



Scrypt:





Next step is setting up my Digibyte block explorer + richlist, but that may need to wait for a little bit as I have a project for MYR that needs doing. But when it gets done, I'll be editing my nodes to point to my block explorer instead of altexplorer.net. Which means that they will need to be briefly restarted, but I'll pop in here & on reddit to let you guys know.



Cheers!



Edit: I should also mention that in order to make the nodes work, you need to install both the digibyte subsidy and (for everything but sha) the python hash module (ex the groestl_hash folder). Hey guys, I just finished the source code & my p2pool nodes for Digibyte's new algos! Complete with testnet networksThe p2pools throw an "out of memory" error if you try launching them, but I believe that's because there is currently no work available from the new algorithms. MAKE ABSOLUTELY SURE that you set the correct algorithm in the digibyte.conf file, stop the daemon and restart it after saving. Blocks found under the wrong algorithm will NOT BE ACCEPTED by the network! (Ex your daemon is sending work out for qubit and you're hashing with sha256).I'll be releasing the source at the bottom of this post, but I would appreciate if you guys would mine on my nodes (I spent quite a few hours preparing the code & the nodes, and I'm setting the fee to a low 0.5%) to support me and my work. Donations would also be appreciatedIf there are any bugs, please open an issue on the github repo (wasn't able to thoroughly test due to no testnet being up), and if you would like your node added as a bootstrap, please submit a pull request in the github repo with your node's address added as a bootstrap.Also, my nodes are located in the USA, on the east coast near Boston.Links to my nodes (They are down right now, but will be live once Multi-algo goes live):SHA256: http://birdspool.no-ip.org:5011/static/stats/ Groestl: http://birdspool.no-ip.org:5021/static/stats/ Skein: http://birdspool.no-ip.org:5031/static/stats/ Qubit: http://birdspool.no-ip.org:5041/static/stats/ Links to the source code:SHA256: https://github.com/birdonwheels5/p2pool-dgbsha Groestl: https://github.com/birdonwheels5/p2pool-dgbGroestl Skein: https://github.com/birdonwheels5/p2pool-dgbSkein Qubit: https://github.com/birdonwheels5/p2pool-dgbQubit Scrypt: https://github.com/birdonwheels5/p2pool-dgbScrypt (added as an extra)Next step is setting up my Digibyte block explorer + richlist, but that may need to wait for a little bit as I have a project for MYR that needs doing. But when it gets done, I'll be editing my nodes to point to my block explorer instead of altexplorer.net. Which means that they will need to be briefly restarted, but I'll pop in here & on reddit to let you guys know.Cheers!Edit: I should also mention that in order to make the nodes work, you need to install both the digibyte subsidy and (for everything but sha) the python hash module (ex the groestl_hash folder). MYR: MNYERWCHqrH1EkGNpF4T8o8dGB391A5jmm

DGB: DKqUZR8ajzo1vkXYWWx476wRyZ4La76WBy