 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
|
Again, blockchain sync problem :
Current block
- on bittrex is 2225505
- on insight-myr.cryptap.us is 2225645
- on miningpoolhub 2225645
- on suprnova 2225505
- on my wallets 2225505
|
|
|
|
"subver": "/Satoshi:0.11.3.2/",
"startingheight": 2223960,
which chain it's correct? You're right there is problem with some wallets, they are not on the same chain. cryptap.us, miningpoolhub.com are on the same chain But not bittrex, suprnova, zpool and myself which are on different chain! |
|
|
|
The pool wallets has been updated, thanks! |
|
|
|
Is there any site with a kind of pie chart showing the distribution of the pools hashrates?
Not a pie chart, but a table https://www.miners-pool.eu/mining-breakdown/DGBI can report only known pool addresses (pool owners can give me their address). |
|
|
|
We just released v6.14.2 which fixes the wallet loading delay where a wallet might take 20+ minutes to open
Thanks for this fix, I was impacted by this issue. Much better, less than 2min to load instead of 20 for the previous version. |
|
|
|
All pools has been updated to 6.14.1 version |
|
|
|
This market will be removed on Friday, September 23rd 2016. The blockchain is no longer operational. If you would like to keep the market listed, please encourage the development team to contact us at support@bittrex.com. There's still hope dev should contact bittrex immediately and help fix known issues on the blockchain. There is no new block since 30 hours. Blake's blocks are almost only mined (but the wallet accept only 3 consecutive blocks with the same algorithm), this coin is probably dead  |
|
|
|
MYR is forked! Start mining with your CPU now.  First yescrypt blocks mined, you can join our pool. Remember, all fee (1%) are distributed to Sea Shepheard organization |
|
|
|
Myriad 0.11.3.1This release introduces Yescrypt mining, changes the Myriad ticker to XMY and activates BIP65/BIP66. 1. Disables Qubit and enables Yescrypt mining.Activates after block 1764000 (estimated early Aug) when 750 of 1000 blocks mined using 0.11.3. (Testnet block 300) Forks from 0.11.2 clients. 2. Myriad ticker changeChanges from MYR to XMY to avoid confusion with Malaysian Ringgit. 3. BIP65/BIP66 activationActivates when 750 of last 1000 blocks are mined using 0.11.3. (Testnet 51 of 100 blocks) Forks from 0.9.x clients. If you are currently running v0.9.x it is recommended to update immediately as there could be a hard-fork for v0.9.x versions at any time. If you are running v0.11.x you should update before August. Download links: http://myriadcoin.org/en/walletshttps://github.com/myriadteam/myriadcoin/releases/tag/v0.11.3.1 All pool wallets are upgraded. We added Yescrypt algorithm for the next fork. |
|
|
|
|
Hello,
try this nodes : 198.50.217.13 (on your list, but I'm connected to), 87.98.178.140
|
|
|
|
Why when I try and send some coins it say transaction to large?
Because transaction cannot contain more than x blocks. If the incoming coins into your wallet are small amounts, you can't send large amount (which is created from your incoming blocks) |
|
|
|
We decided to give all fees collected to the organization Sea Shepherd (for an illimited time). We use the Shapeshift system and we transfer directly the DGB collected to the Sea Shepherd BTC address as you can see on this report http://www.miners-pool.eu/#!/sea-shepherdMiners, if you want to support this organization, you know what you have to do  The collected DGB address is available, you can send coins to this address, it will be converted for the next run. |
|
|
|
We have pushed out v4.0.2 to several servers and seed nodes and it appears to have dramatically improved the reorg issues and propogation problems. Things are looking much better. http://digiexplorer.info/Good, I updated the wallets. Hope this update resolves issues Edit: really better, thank you guys! |
|
|
|
I've added new (4.0.1) nodes manually on all suprnova pools now to get the orphan rate down, however my logs are still full of old "misbehaving" versions...
Hope this new version gonna clean the network! Same as you ocminer, logs are full of "obsolete version". |
|
|
|
miners-pool.eu is finding nothing but orphans on qubit, nobody is mining skein or groestl on there.
Most of blocks found are rejected by the network later... I used 3 different wallets location, all of them on a powerful server with good Internet connection. Now this coin is too fast. Only the most powerful pool can find blocks. Jared I'm not sure than reducing the block target to 15s was a good idea. I got the same problem: wallet v.4.0, scrypt algo, pool reports 300 found blocks, but actually I receive only 30 of them. 90% was rejected on the network. Looks weird. Dev D6Mjh5H7WjPVAg1626Apgk8ELmzhagXZDr here is my address, you can check it. There is some thing wrong with wallet, for example, sharkcoin got 20 second block target, and I got only 5% orphans on it. And again, the block target is >1 minute on each algo, so it doesn't matter. Or maybe you implement the same feature, as digital coin does: • Algorithm Control - If the last three blocks were discovered by the same algorithm, the fourth block will be rejected until its found by one of the other two algorithms. This prevents directed attacks on the network from any single algorithm. Or the goldcoin-like shield: only 6 blocks per 5 minutes(or something loke that), the rest will be orphaned anyway by the wallet? That will explain everything. It appears there is a fair amount of mining still occurring on the v3.0 wallets. We are working on an update to auto disconnect these peers. This should help with the orphan rate dramatically. In the mean time transactions are still getting processed normally. Here is the patch (not official) to refuse old peer versions : https://github.com/Metice/digibyte/commit/fb7ad7dfdf045157573204259665d69eb76c8c20 |
|
|
|
miners-pool.eu is finding nothing but orphans on qubit, nobody is mining skein or groestl on there.
Most of blocks found are rejected by the network later... I used 3 different wallets location, all of them on a powerful server with good Internet connection. Now this coin is too fast. Only the most powerful pool can find blocks. Jared I'm not sure than reducing the block target to 15s was a good idea. |
|
|
|
160 orphans, 65% of Digibyte network since 1 hour. Oups |
|
|
|
There is no filter, old wallet version can connect to the new one many peers 3.0x are still connected, even if you restart the wallet. |
|
|
|
|
