Can someone link the windows wallet download please, the one on the first page isn't working.
Thanks,
Topic: [ANN] Diamond DMD - new PoW/PoS coin | Super random blocks | Only 4.38 mil total - page 10. (Read 116383 times)
December 09, 2013, 08:43:14 AM
December 09, 2013, 07:00:00 AM
Can someone please state some working nodes.
These are the ones I got in my conf file:
addnode=27.3.56.138
addnode=84.237.202.34
addnode=121.206.245.183
addnode=70.98.114.237
addnode=97.89.174.206
Thank you.
These are the ones I got in my conf file:
addnode=27.3.56.138
addnode=84.237.202.34
addnode=121.206.245.183
addnode=70.98.114.237
addnode=97.89.174.206
Thank you.
December 09, 2013, 06:48:51 AM
Have you contacted Sheinsha? It looks like we need to join force together to ensure that DMD community can resist 51% attack. I believe that most of miners have a rig or rigs of 0.5 - 2MH/s. If someone has rigs of 60 - 80 Mh/s, he can solve all the block himself
I have already contacted with sheinsa and i m waiting for his response...
December 09, 2013, 06:35:56 AM
Have you contacted Sheinsha? It looks like we need to join force together to ensure that DMD community can resist 51% attack. I believe that most of miners have a rig or rigs of 0.5 - 2MH/s. If someone has rigs of 60 - 80 Mh/s, he can solve all the block himself
December 09, 2013, 06:24:35 AM
I suggest gathering all our hashing power to one of our mining pools... Does it have any chance?
December 09, 2013, 06:10:16 AM
Hi,
I tried to do solo mining myself by no hope. All my block submission is rejected.
I got 7-8 active connections to Diamond networks. No sure if there is someone out there who has a massive power of computing verifies transactions much faster than me.
I tried to do solo mining myself by no hope. All my block submission is rejected.
I got 7-8 active connections to Diamond networks. No sure if there is someone out there who has a massive power of computing verifies transactions much faster than me.
December 09, 2013, 05:57:16 AM
Hello all, we are trying to identify the coin network issue. Anyone who can help is more than welcome.
December 09, 2013, 02:59:22 AM
dmdpool can not resolve any block for several hours. Also, the speed of block generation on dmdpool is very slow: 183 blocks per 24 hours. It looks like Diamond has been a victim of 51% attak
December 09, 2013, 02:05:28 AM
blockchain has forked or something happened (100% rejects)
I'm seeing the same thing. The diff in CGMiner looks strange too. Showing 12K but resetting to 491.
December 08, 2013, 11:49:45 PM
blockchain has forked or something happened (100% rejects)
December 08, 2013, 10:49:45 PM
Just tried downloading this wallet, and got the error "Warning:Checkpoint is too old. Wait for the block chain to download, or notify the developers"
I got the same thing, stuck on block 61246 for a while, but it just started downloading again. Make sure you have the addnodes included in your config file, I always add my pools as nodes as well
December 08, 2013, 10:01:29 PM
Just tried downloading this wallet, and got the error "Warning:Checkpoint is too old. Wait for the block chain to download, or notify the developers"
December 07, 2013, 10:33:41 PM
PoS specification?
December 04, 2013, 12:26:58 PM
thx for update, still showing warning in qt client checkpoint is too old etc....
New version is coming soon
December 04, 2013, 08:42:27 AM
thx for update, still showing warning in qt client checkpoint is too old etc....
December 03, 2013, 06:59:16 PM
- windows client download 1.1 link on mega is invalid
- main home page also invalid.
kind of hard to trust or support a new coin if 2 of the primary links in the announcement are invalid or dead.
c'mon guys...
- main home page also invalid.
kind of hard to trust or support a new coin if 2 of the primary links in the announcement are invalid or dead.
c'mon guys...
We are really sure that many ppl join to DMD dev community.
The first step is to update the DMD wallet/client. So after integration of new version, we will announce new website and download links.
Until then, here is a link for the current wallet version:
https://mega.co.nz/#!BsgWzBQa!UvSMyib1mClsjjv5mS_zEgeDYcw6PnAEKO4p-fMgxeo
December 03, 2013, 04:21:28 PM
just an idea...
can you rollback your installation, send the coins to a new wallet address
load the new installation with the new wallet
let the blockchain do its work and the coins will transfer?
can you rollback your installation, send the coins to a new wallet address
load the new installation with the new wallet
let the blockchain do its work and the coins will transfer?
have done this already, I have deleted all nodes from the config file.
sometimes too many addnodes crashes the client
try removing the nodes and adding them in the debug command line window
try removing the nodes and adding them in the debug command line window
Hello, can anybody help me ? In my wallet are 1000DMD mined and I have also the same problem with the newest client. It crashes on every start after one minute or earlier.
What I´ve done already to try to solve the problem:
-Deleted all data in roaming except the wallet.dat
-Updated the to the new client
If I delete my wallet.dat and try to start the client, it works fine, but then my DMD´s are lost.
I give 100 DMD to the Solver of my problem.
What I´ve done already to try to solve the problem:
-Deleted all data in roaming except the wallet.dat
-Updated the to the new client
If I delete my wallet.dat and try to start the client, it works fine, but then my DMD´s are lost.
I give 100 DMD to the Solver of my problem.
full member
Activity: 192
Merit: 100
bitcoin-world.de - The european information source
December 03, 2013, 03:07:10 PM
have done this already, I have deleted all nodes from the config file.
sometimes too many addnodes crashes the client
try removing the nodes and adding them in the debug command line window
try removing the nodes and adding them in the debug command line window
Hello, can anybody help me ? In my wallet are 1000DMD mined and I have also the same problem with the newest client. It crashes on every start after one minute or earlier.
What I´ve done already to try to solve the problem:
-Deleted all data in roaming except the wallet.dat
-Updated the to the new client
If I delete my wallet.dat and try to start the client, it works fine, but then my DMD´s are lost.
I give 100 DMD to the Solver of my problem.
What I´ve done already to try to solve the problem:
-Deleted all data in roaming except the wallet.dat
-Updated the to the new client
If I delete my wallet.dat and try to start the client, it works fine, but then my DMD´s are lost.
I give 100 DMD to the Solver of my problem.
December 03, 2013, 03:04:56 PM
sometimes too many addnodes crashes the client
try removing the nodes and adding them in the debug command line window
dQZiFTiKyVRPygdrW58muC3yNRBZheWj6z
try removing the nodes and adding them in the debug command line window
dQZiFTiKyVRPygdrW58muC3yNRBZheWj6z
Hello, can anybody help me ? In my wallet are 1000DMD mined and I have also the same problem with the newest client. It crashes on every start after one minute or earlier.
What I´ve done already to try to solve the problem:
-Deleted all data in roaming except the wallet.dat
-Updated the to the new client
If I delete my wallet.dat and try to start the client, it works fine, but then my DMD´s are lost.
I give 100 DMD to the Solver of my problem.
What I´ve done already to try to solve the problem:
-Deleted all data in roaming except the wallet.dat
-Updated the to the new client
If I delete my wallet.dat and try to start the client, it works fine, but then my DMD´s are lost.
I give 100 DMD to the Solver of my problem.
full member
Activity: 192
Merit: 100
bitcoin-world.de - The european information source
December 03, 2013, 02:59:07 PM
Hello, can anybody help me ? In my wallet are 1000DMD mined and I have also the same problem with the newest client. It crashes on every start after one minute or earlier.
What I´ve done already to try to solve the problem:
-Deleted all data in roaming except the wallet.dat
-Updated the to the new client
-repair-wallet through the debug console -> check was OK
-deleted all nodes in the config.
If I delete my wallet.dat and try to start the client, it works fine, but then my DMD´s are lost.
I give 100 DMD to the Solver of my problem.
this is db.log :
file wallet.dat has LSN 41/7885761, past end of log at 1/1418101
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 41/7885761 past current end-of-log of 1/1418101
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 10
txn_checkpoint: failed to flush the buffer cache: DB_RUNRECOVERY: Fatal error, run database recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
What I´ve done already to try to solve the problem:
-Deleted all data in roaming except the wallet.dat
-Updated the to the new client
-repair-wallet through the debug console -> check was OK
-deleted all nodes in the config.
If I delete my wallet.dat and try to start the client, it works fine, but then my DMD´s are lost.
I give 100 DMD to the Solver of my problem.
this is db.log :
file wallet.dat has LSN 41/7885761, past end of log at 1/1418101
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 41/7885761 past current end-of-log of 1/1418101
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 10
txn_checkpoint: failed to flush the buffer cache: DB_RUNRECOVERY: Fatal error, run database recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
Jump to: