Thank you for having us onboard.
Open beta launch. Pair featured: DGB/BTC.
Pre-register for beta here: https://bitfineon.com |
|
|
|
How to export my wallet from DigiByte Сore?
I can not understand where to get secret words, I want to transfer my wallet to a mobile application.
You can only dump your private key! Open the DGB core wallet app
Go to Help -> Debug Window
Select "Console" tab
Type "dumpprivkey [public key]" and press ENTER |
|
|
|
can someone post nodes list, i cant connect to the chain. Thanks!
|
|
|
|
Hello, We have created a group of Baikal Miners owners where we can share information, solve problems that occur or sell and buy machines. It is difficult to contact baikal support and solve the problem right away. There is also a lot of threads in the forums, but it is impossible to read and ask everywhere. This group can help us all. The more we get the better. So if you want, join and add your friends to the facebook group: Baikalminer discuss/share/experience https://www.facebook.com/groups/145674359425246/Please support this new Pool: http://mineblocks.co.uk/getting_startedUse this: alqo ALQOquark stratum.mineblocks.co.uk Port: 3075, Diff: 1 Core Wallet: https://alqo.org/#downloadsThis is a very promising projekt.Support for pool is very helpfull @ : https://t.me/mineblockspFee is 0.5 % payments every 20 min when block is confirmed Price for ALQO is getting bigger. They will change to POS. But first you can mine it! https://coinmarketcap.com/currencies/alqo/PoW Block Rewards, Reward Allocation (Starting at the 10. November) Block 2 - 86400 = 200 ALQO Masternodes 20% / Miners 80% Block 86401 - 151200 = 150 ALQO Masternodes 25% / Miners 75% Block 151201 - 302400 = 125 ALQO Masternodes 30% / Miners 70% Block 302401 - 345600 = 100 ALQO Masternodes 35% / Miners 65% Block 345601 - 388800 = 75 ALQO Masternodes 40% / Miners 60% Block 388801 - 475200 = 50 ALQO Masternodes 40% / Miners 60% https://alqo.org/block-reward/More Infos @ https://bitcointalk.org/index.php?topic=2343884.0 |
|
|
|
DOWN AGAIN?
502 Bad Gateway!!! Please Fix your Server ASAP. Thank You. |
|
|
|
Solomining on new Digibyte core wallet v6.14.2
In Digibyte v6.14.2 "getwork" is gone. It now uses getblocktemplate.
So if you want to mine on the new wallet you have to change your configs!
These instructions are for people that already know how to solo mine.
LINUX:Step 1. Generate an rpcauth code to put in your digibyte.conf file by going to this link https://github.com/digibyte/digibyte/tree/6.14.0/share/rpcuser and download and put the file in your digibyte root folder. Step 2. Run it by typing “python ./rpcuser.py [user]” ([user] can be what you choose to put in)It will show you something like this. “String to be appended to digibyte.conf: rpcauth=user:1335d15a52c8c24ef246b73bf4b9741$44d37ba0cb46191f11749c3217c7e497da5e01f8e8e01bd501bb35fbfcc0c9ba Your password: l147_CovTnVvV4P0W5p8qa1B5Gs88EDqMo5OI9Fmo8Y= “ Step 3. Remove rpcuser/rpcpassword from your existing digibyte.conf file. Step 4. Put the rpcauth=user:1335d15a52c8c24ef246b73bf4b9741$44d37ba0cb46191f11749c3217c7e497da5e01f8e8e01bd501bb35fbfcc0c9ba in your digibyte.conf file Use the password for your mining rig for example. -u user -p l147_CovTnVvV4P0W5p8qa1B5Gs88EDqMo5OI9Fmo8Y= WINDOWS:Step 1. You cant generate an rpcauth code because you need to install python first. So the easiest way ist to use existing rpcauth. Step 2. Remove rpcuser/rpcpassword from your existing digibyte.conf file. Step 3. Put the rpcauth=user:1335d15a52c8c24ef246b73bf4b9741$44d37ba0cb46191f11749c3217c7e497da5e01f8e8e01bd501bb35fbfcc0c9ba in your digibyte.conf file This is the digibyte.conf:
server=1
listen=1
rpcport=14022
rpcallowip=192.168.222.0/24
algo=qubit
rpcauth=user:1335d15a52c8c24ef246b73bf4b9741$44d37ba0cb46191f11749c3217c7e497da5e01f8e8e01bd501bb35fbfcc0c9ba rpcallowip=192.168.222.0/24 => You can change this to your Network or only one IP in your LAN! algo=qubit => change algo you want to mine digibyte.conf file has to be in your digibyte folder. => C:\Users\accountname\AppData\Roaming\DigiByte Step 4. Change your bat or config for your miner! At this example i use algo=qubit so i want to mine qubit. I use the cpuminer. If you use other algo and other miners just read the help.txt which comes with your miningsoftware! This is the mining.bat for cpuminer:
cpuminer -a qubit --url=192.168.222.202:14022 -u user -p l147_CovTnVvV4P0W5p8qa1B5Gs88EDqMo5OI9Fmo8Y= --no-stratum --no-getwork --no-extranonce --coinbase-addr=D8i1mDnjqpXGwyCrFJT9qbSYuYtdoW7bJc Use the gernerated password and the user with the name user! -u user -p l147_CovTnVvV4P0W5p8qa1B5Gs88EDqMo5OI9Fmo8Y=  INFO:
-n, --nfactor neoscrypt N-Factor
--coinbase-addr=ADDR payout address for solo mining
--coinbase-sig=TEXT data to insert in the coinbase when possible
--no-longpoll disable long polling support
--no-getwork disable getwork support
--no-gbt disable getblocktemplate support
--no-stratum disable X-Stratum support
--no-extranonce disable Stratum extranonce support
--no-redirect ignore requests to change the URL of the mining server
p.s. big thx also to twebit |
|
|
|
Solomining on new Digibyte core wallet v6.14.2
In Digibyte v6.14.2 "getwork" is gone. It now uses getblocktemplate.
So if you want to mine on the new wallet you have to change your configs!
These instructions are for people that already know how to solo mine.
LINUX:Step 1. Generate an rpcauth code to put in your digibyte.conf file by going to this link https://github.com/digibyte/digibyte/tree/6.14.0/share/rpcuser and download and put the file in your digibyte root folder. Step 2. Run it by typing “python ./rpcuser.py [user]” ([user] can be what you choose to put in)It will show you something like this. “String to be appended to digibyte.conf: rpcauth=user:1335d15a52c8c24ef246b73bf4b9741$44d37ba0cb46191f11749c3217c7e497da5e01f8e8e01bd501bb35fbfcc0c9ba Your password: l147_CovTnVvV4P0W5p8qa1B5Gs88EDqMo5OI9Fmo8Y= “ Step 3. Remove rpcuser/rpcpassword from your existing digibyte.conf file. Step 4. Put the rpcauth=user:1335d15a52c8c24ef246b73bf4b9741$44d37ba0cb46191f11749c3217c7e497da5e01f8e8e01bd501bb35fbfcc0c9ba in your digibyte.conf file Use the password for your mining rig for example. -u user -p l147_CovTnVvV4P0W5p8qa1B5Gs88EDqMo5OI9Fmo8Y= WINDOWS:Step 1. You cant generate an rpcauth code because you need to install python first. So the easiest way ist to use existing rpcauth. Step 2. Remove rpcuser/rpcpassword from your existing digibyte.conf file. Step 3. Put the rpcauth=user:1335d15a52c8c24ef246b73bf4b9741$44d37ba0cb46191f11749c3217c7e497da5e01f8e8e01bd501bb35fbfcc0c9ba in your digibyte.conf file This is the digibyte.conf:
server=1
listen=1
rpcport=14022
rpcallowip=192.168.222.0/24
algo=qubit
rpcauth=user:1335d15a52c8c24ef246b73bf4b9741$44d37ba0cb46191f11749c3217c7e497da5e01f8e8e01bd501bb35fbfcc0c9ba rpcallowip=192.168.222.0/24 => You can change this to your Network or only one IP in your LAN! algo=qubit => change algo you want to mine digibyte.conf file has to be in your digibyte folder. => C:\Users\accountname\AppData\Roaming\DigiByte Step 4. Change your bat or config for your miner! At this example i use algo=qubit so i want to mine qubit. I use the cpuminer. If you use other algo and other miners just read the help.txt which comes with your miningsoftware! This is the mining.bat for cpuminer:
cpuminer -a qubit --url=192.168.222.202:14022 -u user -p l147_CovTnVvV4P0W5p8qa1B5Gs88EDqMo5OI9Fmo8Y= --no-stratum --no-getwork --no-extranonce --coinbase-addr=D8i1mDnjqpXGwyCrFJT9qbSYuYtdoW7bJc Use the gernerated password and the user with the name user! -u user -p l147_CovTnVvV4P0W5p8qa1B5Gs88EDqMo5OI9Fmo8Y= INFO:
-n, --nfactor neoscrypt N-Factor
--coinbase-addr=ADDR payout address for solo mining
--coinbase-sig=TEXT data to insert in the coinbase when possible
--no-longpoll disable long polling support
--no-getwork disable getwork support
--no-gbt disable getblocktemplate support
--no-stratum disable X-Stratum support
--no-extranonce disable Stratum extranonce support
--no-redirect ignore requests to change the URL of the mining server
p.s. big thx to twebit! |
|
|
|
When you lack of luck... you lack of luck!
This is my story, the story of a guy who has already believe in DGB and who was holding approximately 2300000 DGB for 2 years and a half. Unjobless for several months, I had to sell my DGB in november 2016 for a price of approximately 800€. Now, the explosion of DGB combined to the one of BTC just killed me : 2300000 DGB is worth now 93000€.
I want to kill myself. Because of poverty, I had to sell my DGB... the only digital currency I had faith on. Sad life... really, sad life...
Nice to hear from you MOXYmore. Hope you getting better! Welcome back. I have a job right now... but really, I'm disguted of so much waiting time and faith on Digibyte, to sell them all because of difficulties IRL. Good job for the holders... for me, it's time to accept the fact that this life just wanna makes me poor all my life. See ya boys... Its not about money, its about yourself. Be confident, trust in you, give positiv fibes and you will recive what you give and what you want. What you push out it will come back to you soon or later! You creating REALITY! |
|
|
|
so is this coin a waste of time?
NO, its only long hold people dont get it. |
|
|
|
When you lack of luck... you lack of luck!
This is my story, the story of a guy who has already believe in DGB and who was holding approximately 2300000 DGB for 2 years and a half. Unjobless for several months, I had to sell my DGB in november 2016 for a price of approximately 800€. Now, the explosion of DGB combined to the one of BTC just killed me : 2300000 DGB is worth now 93000€.
I want to kill myself. Because of poverty, I had to sell my DGB... the only digital currency I had faith on. Sad life... really, sad life...
Nice to hear from you MOXYmore. Hope you getting better! Welcome back. |
|
|
|
Hi, use old wallet 4.0.3 as server or try to use new rpc auth!
We already had this discussion early on Telegram.
You need new rpcauth method!https://github.com/digibyte/digibyte/tree/6.14.0/share/rpcuserGary Mckee, [25.03.17 16:06] that branch is ahead of 5.4.2 Gary Mckee, [25.03.17 16:06] rpcuser/rpcpassword should still work twebit, [25.03.17 16:06] the thing is I mine with the old deamon no problem but the new way of mining has changed something and rpcuser/rpcpassword doesn't work now Gary Mckee, [25.03.17 16:06] https://github.com/digibyte/digibyte/tree/6.14.0/share/rpcuserGary Mckee, [25.03.17 16:07] so ./rpcuser user Gary Mckee, [25.03.17 16:07] will generate an auth for you to put in your digibyte.conf twebit, [25.03.17 16:07] I generated the .cookie file and put it in my config twebit, [25.03.17 16:08] already twebit, [25.03.17 16:08] rpcauth=_cookie_:numbers Gary Mckee, [25.03.17 16:08] whats your digibyte.conf look like twebit, [25.03.17 16:09] server=1 listen=1 deamon=1 algo=sha256d rpcauth=__cookie__:thenumber rpcpassword=thepw rpcallowip=192.168.1.12/24 rpcport=14022 port=12024 maxconnections=10 addnode=46.4.66.6 Gary Mckee, [25.03.17 16:10] what are you using for bfgminer password Gary Mckee, [25.03.17 16:10] should be no need for rpcpassword Gary Mckee, [25.03.17 16:11] if you have rpcauth twebit, [25.03.17 16:11] thepw (its a long number) Gary Mckee, [25.03.17 16:11] so if you run the script i linked before Gary Mckee, [25.03.17 16:11] the output is Gary Mckee, [25.03.17 16:11] String to be appended to digibyte.conf: rpcauth=user:5958c94d2bfd7eca2db5cfd126fc7eb1$2b2b0f060afc89ce848d7a9a006eecbe4776e3271d533665e1504f3236ea20ef Your password: C-lqqs6x3gayJwBqPr_wxjAoQ3Gm82L45HQ6zN6l6d8= Gary Mckee, [25.03.17 16:11] rpcauth=user:5958c94d2bfd7eca2db5cfd126fc7eb1$2b2b0f060afc89ce848d7a9a006eecbe4776e3271d533665e1504f3236ea20ef Gary Mckee, [25.03.17 16:11] is what you would put in digibyte.conf Gary Mckee, [25.03.17 16:11] but Gary Mckee, [25.03.17 16:11] C-lqqs6x3gayJwBqPr_wxjAoQ3Gm82L45HQ6zN6l6d8= Gary Mckee, [25.03.17 16:11] is what you would use for bfgminer twebit, [25.03.17 16:12] oh no I copied it from the text file cookie eg; __cookie__:the long number Gary Mckee, [25.03.17 16:12] yeah that's probably why Gary Mckee, [25.03.17 16:12] try adding the rpcauth command i just posted into digibyte.conf Gary Mckee, [25.03.17 16:13] close/restart wallet Gary Mckee, [25.03.17 16:13] and use C-lqqs6x3gayJwBqPr_wxjAoQ3Gm82L45HQ6zN6l6d8= as your bfgminer password twebit, [25.03.17 16:13] ok so user:longnumber into the config ah ok and the pw for bfgminer OK I'll be back in 10 minutes while I startup again Gary Mckee, [25.03.17 16:14] also remove rpcpassword twebit, [25.03.17 16:15] what about the bfgminer user still the same I have digibyterpc as the user now twebit, [25.03.17 16:15] ok Gary Mckee, [25.03.17 16:15] user will be 'user' twebit, [25.03.17 16:15] ok twebit, [25.03.17 16:21] and then that same long number in my bfgminer for pw? twebit, [25.03.17 16:22] starting now will be 10 miutes Gary Mckee, [25.03.17 16:22] nah Gary Mckee, [25.03.17 16:22] gonna PM you twebit, [25.03.17 16:22] ok Mike Jumbley, [25.03.17 16:50] Don’t forget to document it all twe. 😊 twebit, [25.03.17 16:50] I won't 😊
|
|
|
|
hello guys
can someone help me to choose miner-pool and how to setup the .bat file for digibyte please?
i mine with gpu rx 480
OK use sgminer. |
|
|
|
HR Trust: -2: -1 / +0 Warning: Trade with extreme caution! Unignore Re: ★★DigiByte|极特币★★[DGB]✔ DigiSync v6.14.2 - DigiSpeed - Segwit -DiguSign Today at 06:06:38 PM Show/Hide This user is currently ignored.Show/Hide first time i used it!  |
|
|
|
do linux x64 =>xp 32 wont work
Why? There is a previous version of digibyte core?
http://digibyte.co/digibyte-walletsx86 Wallet having Problem so use please x64 Wallet.
Thank you. |
|
|
|
|
do linux x64 =>xp 32 wont work
|
|
|
|
my digibyte.config
rpcauth=bycag:5drfd59a7d8a7fd953022fcfabf2121$58a7a7myauth8a7b6d203e093db8a30a3c305c9cb5
Your password:GHF2qp4Pmypassb99kh1iBM=
server=1
listen=1
deamon=1
rpcallowip=127.0.0.1
rpcport=14022
port=12024
maxconnections=10
txindex=1
algo=groestl
my config:
{
"pools" : [
{
"url" : "127.0.0.1:14022",
"user": "bycag:5drfd59a7d8a7fd953022fcfabf2121$58a7a7myauth8a7b6d203e093db8a30a3c305c9cb5",
"pass" : "GHF2qp4Pmypassb99kh1iBM="
}
]
,
"intensity" : "20,20,20,18",
"worksize" : "128,128,128,128",
"kernel" : "myriadcoin-groestl",
"lookup-gap" : "2,2,2,2",
"thread-concurrency" : "8192,8192,8192,8192",
"shaders" : "0,0,0,0",
"gpu-threads" : "2,2,2,2",
"gpu-engine" : "1000,1000,1000,925",
"gpu-fan" : "80,80,80,80",
"gpu-memclock" : "170,170,170,150",
"gpu-memdiff" : "0,0,0,0",
"gpu-powertune" : "0,0,0,0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "95,95,95,95",
"temp-overheat" : "85,85,85,85",
"temp-target" : "75,75,75,75",
"api-mcast-port" : "4028,4028,4028,4028",
"api-port" : "4028,4028,4028,4028",
"expiry" : "28,28,28,28",
"failover-switch-delay" : "60,60,60,60",
"gpu-dyninterval" : "7,7,7,7",
"gpu-platform" : "0",
"log" : "5,5,5,5",
"no-pool-disable" : true,
"queue" : "1,1,1,1",
"scan-time" : "7,7,7,7",
"tcp-keepalive" : "30,30,30,30",
"temp-hysteresis" : "3,3,3,3",
"shares" : "0,0,0,0",
"kernel-path" : "/usr/local/bin"
}
I generated rpcauth and password, and no work, where am I wrong ?
digibyte.config rpcauth=bycag:5drfd59a7d8a7fd953022fcfabf2121$58a7a7myauth8a7b6d203e093db8a30a3c305c9cb5 server=1 listen=1 deamon=1 rpcallowip=127.0.0.1 rpcport=14022 port=12024 maxconnections=10 txindex=1 algo=groestl my config: { "pools" : [ { "url" : "127.0.0.1:14022", "user": "bycag", "pass" : "GHF2qp4Pmypassb99kh1iBM=" } I think this way. Only RPCauth in digibyte.conf and the user with generated password into your minerconfig. |
|
|
|
We got to keep pushing Chinese Exchanges, were very close, but I am not satisfied with close, nor any of us, so let's keep pushing, OKcoin, BTER, BTC38, and BTCC, all 4 have emailed Discovernow Digibyte back this year, so there getting aware, but Please all you guys, tweet them out, show our Volume.
Once we get China, we will work on Japan |
|
|
|
|
Show Posts
