There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, but full nodes are more resource-heavy, and they must do a lengthy initial syncing process. As a result, lightweight clients with somewhat less security are commonly used. Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here. Advertised sites are not enorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.

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 #10902



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

ycagel



Offline



Activity: 910

Merit: 1000







Hero MemberActivity: 910Merit: 1000 Re: ★★ DigiByte ★★ [DGB] ✈ ✔ MultiAlgo v3.0.1 officially released! Mandatory Update! August 20, 2014, 01:30:48 AM #10903



YC





Quote from: birdonwheels5 on August 20, 2014, 12:56:59 AM



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 our 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 (The 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 our 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 (The 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). Awesome work!YC

tdcooper99



Offline



Activity: 215

Merit: 100







Full MemberActivity: 215Merit: 100 Re: ★★ DigiByte ★★ [DGB] ✈ ✔ MultiAlgo v3.0.1 officially released! Mandatory Update! August 20, 2014, 09:02:57 AM #10911

I know I keep beating what very well may be a dead dog, but ffs I'd like to be able to solo mine at least one block to know I've done it right. Got the new wallet compiled on Ubuntu 14.04, it happily syncs. I have pointed 85MH/s at it from 2 separate miners on my LAN, so to be clear I am trying to solo mine via the wallet remotely. My conf allows this by setting rpcallow=*.



Have let it run for 18 hours now... nothing. With 85MH/s at the current difficulty, the expected time to find a block is around 4 hours. So, even allowing double that I should have found at least 2. I'm sure it's something crazy simple. As you can see, I am running cgminer 4.3.5. The only thing different about it is it's been compiled for Zeusminer support.



Code: rpcallowip=*

rpcuser=xxxxxx

rpcpassword=xxxxx

listen=1

server=1

daemon=1

txindex=1

debug=1

algo=scrypt

rpcport=14022

port=12024

addnode=216.250.125.121

addnode=74.208.230.160

addnode=74.112.204.202

addnode=46.4.32.220

addnode=198.27.109.88

addnode=54.204.36.33

addnode=198.41.184.140

addnode=144.76.94.182

addnode=95.85.50.188

addnode=162.159.240.70

My miner is seeing block changes on the network:



Code: cgminer version 4.3.5 - Started: [2014-08-20 04:02:40]

--------------------------------------------------------------------------------

(5s):0.000 (1m):0.000 (5m):0.000 (15m):0.000 (avg):0.000h/s

A:0 R:0 HW:53 WU:0.0/m

Connected to 10.20.30.214 diff 20.8M with LP as user u*******r

Block: 7876fe40... Diff:316 Started: [07:40:48] Best share: 0

--------------------------------------------------------------------------------

[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit

0: ZUS ttyUSB0: 256 chips 220 MHz | 0.000 / 0.000h/s WU:0.0/m

--------------------------------------------------------------------------------

[2014-08-20 06:56:39] Network diff set to 84

[2014-08-20 06:56:45] Block height change to 141954 detected on pool 0

[2014-08-20 06:56:45] Network diff set to 112

[2014-08-20 06:57:10] Block height change to 141955 detected on pool 0

[2014-08-20 06:57:10] Network diff set to 150

[2014-08-20 06:57:17] Block height change to 141956 detected on pool 0

[2014-08-20 06:57:17] Network diff set to 200

[2014-08-20 06:57:22] Block height change to 141957 detected on pool 0

[2014-08-20 06:57:22] Network diff set to 267

[2014-08-20 06:57:30] Block height change to 141959 detected on pool 0

[2014-08-20 06:57:30] Network diff set to 475

[2014-08-20 07:40:48] Block height change to 141960 detected on pool 0

[2014-08-20 07:40:48] Network diff set to 316



I know I keep beating what very well may be a dead dog, but ffs I'd like to be able to solo mine at least one block to know I've done it right. Got the new wallet compiled on Ubuntu 14.04, it happily syncs. I have pointed 85MH/s at it from 2 separate miners on my LAN, so to be clear I am trying to solo mine via the wallet remotely. My conf allows this by setting rpcallow=*.Have let it run for 18 hours now... nothing. With 85MH/s at the current difficulty, the expected time to find a block is around 4 hours. So, even allowing double that I should have found at least 2. I'm sure it's something crazy simple. As you can see, I am running cgminer 4.3.5. The only thing different about it is it's been compiled for Zeusminer support.My miner is seeing block changes on the network:

tdcooper99



Offline



Activity: 215

Merit: 100







Full MemberActivity: 215Merit: 100 Re: ★★ DigiByte ★★ [DGB] ✈ ✔ MultiAlgo v3.0.1 officially released! Mandatory Update! August 20, 2014, 12:22:17 PM #10916

Anyone tried and/or succeeded in compiling a wallet on a Raspberry Pi image? I'm currently trying on MinePeon (ArchLinux). Was going fairly well until I tried to resize my image to create more space so could create swap file.... buggered my image. Unfortunately I'm working remotely from a different city at the moment... no physical access to my miners until next week



Anyone tried and/or succeeded in compiling a wallet on a Raspberry Pi image? I'm currently trying on MinePeon (ArchLinux). Was going fairly well until I tried to resize my image to create more space so could create swap file.... buggered my image. Unfortunately I'm working remotely from a different city at the moment... no physical access to my miners until next week