Topic: [ANN] Diamond (DMD) Takeover! Update v1.0.4 | NEW website, pool, block-explorer - page 32. (Read 50089 times)
December 24, 2013, 07:01:59 AM
cryptsy mate, where i got mine
December 24, 2013, 06:32:04 AM
dadon - where can I buy DMD?
December 24, 2013, 06:05:50 AM
what do you think the price are of these should be at? im holding long term, got myself today just over 5k , am i going to be rich 
December 24, 2013, 05:40:14 AM
I'm probably a bit slow - but what can I use the block explorer for..?
Which columns are interesting..?
Which columns are interesting..?
December 24, 2013, 03:57:15 AM
really underpriced, one block should be valued at 2-3 million satoshi
December 24, 2013, 03:45:50 AM
dmdpool.digsys.bg is PROP not PPLNS.
December 23, 2013, 07:27:22 PM
No PPS pool yet. You may want to look at
dmdpool.net | 1% PPLNS
or
pool.diamondblocks.info| 1% PPLNS
dmdpool.net | 1% PPLNS
or
pool.diamondblocks.info| 1% PPLNS
December 23, 2013, 03:42:27 PM
Just wondering if there are any PPS pools? I didn't see any in the OP but I am not sure if it is kept up to date either.
Thanks in advance
Thanks in advance
December 23, 2013, 09:09:17 AM
Main DMD thread is updated 
December 23, 2013, 06:04:08 AM
http://www.diamondblocks.info is great. Much appreciated
December 22, 2013, 08:51:47 PM
New pool set up! Proceeds here will go to support the Block Explorer (http://www.diamondblocks.info).
The pool website is: http://pool.diamondblocks.info. Fees are 1%. Come support Diamondblocks.info!
--Tripmode
The pool website is: http://pool.diamondblocks.info. Fees are 1%. Come support Diamondblocks.info!
--Tripmode
December 21, 2013, 08:31:27 PM
Hi,
I've just updated from V 1.01 to V1.02 - My conf file looks like this:
11,344 blocks remaining to download - so far, so good (Shame my hashes are lame)
(Is this the full set of Nodes?) Thanks,
dRFU4RMoVuNaLegTLDcf3vL6LzvaRnKaYe
I've just updated from V 1.01 to V1.02 - My conf file looks like this:
Quote
(too much Blah)
11,344 blocks remaining to download - so far, so good (Shame my hashes are lame)
(Is this the full set of Nodes?) Thanks,
dRFU4RMoVuNaLegTLDcf3vL6LzvaRnKaYe
Since I started Diamond up yesterday it's downloaded 8GB of data - something like what BTC is doing - Sould this be happening or is this a glitch?
December 21, 2013, 12:52:42 PM
Hi,
I've just updated from V 1.01 to V1.02 - My conf file looks like this:
listen=1
daemon=1
server=1
rpcuser=Timelord2067
rpcpassword=Muffin
rpcport=17772
rpcconnect=127.0.0.1
addnode=121.206.245.183
addnode=192.241.81.68
addnode=216.155.151.242
addnode=27.3.56.138
addnode=54.201.128.214
addnode=70.98.114.237
addnode=83.212.206.37
addnode=84.237.202.34
addnode=97.89.174.206
addnode=5.249.152.30:17771
addnode=193.68.21.19:17771
11,344 blocks remaining to download - so far, so good (Shame my hashes are lame)
(Is this the full set of Nodes?) Thanks,
dRFU4RMoVuNaLegTLDcf3vL6LzvaRnKaYe
I've just updated from V 1.01 to V1.02 - My conf file looks like this:
Quote
listen=1
daemon=1
server=1
rpcuser=Timelord2067
rpcpassword=Muffin
rpcport=17772
rpcconnect=127.0.0.1
addnode=121.206.245.183
addnode=192.241.81.68
addnode=216.155.151.242
addnode=27.3.56.138
addnode=54.201.128.214
addnode=70.98.114.237
addnode=83.212.206.37
addnode=84.237.202.34
addnode=97.89.174.206
addnode=5.249.152.30:17771
addnode=193.68.21.19:17771
11,344 blocks remaining to download - so far, so good (Shame my hashes are lame)
(Is this the full set of Nodes?) Thanks,
dRFU4RMoVuNaLegTLDcf3vL6LzvaRnKaYe
December 20, 2013, 04:37:14 AM
You can always pool mine (there are now three active pools) while you wait. You don't need a client or synchronization for that.
Anyway, as difficulty increases with price, solo mining may not be a very good option soon, unless you have strong hash power.
Anyway, as difficulty increases with price, solo mining may not be a very good option soon, unless you have strong hash power.
Yes, I probably will. I don't have very high hash power, and I'm not having much luck with DMD. I'm new to solo mining and don't really understand what I see. I see tentative transactions show up, and they get stuck there. If I restart the software they disappear. Are they stale or orphaned? I also see "Number of transactions: 4", but only two transactions are showing. And that's after having at least 5 blocks accepted according to CGWatcher. So I'm confused.
Actually, network has problem few hours before, so it s ok that your miner could not submit blocks successfully. Please give a try now.
December 20, 2013, 12:12:57 AM
You can always pool mine (there are now three active pools) while you wait. You don't need a client or synchronization for that.
Anyway, as difficulty increases with price, solo mining may not be a very good option soon, unless you have strong hash power.
Anyway, as difficulty increases with price, solo mining may not be a very good option soon, unless you have strong hash power.
Yes, I probably will. I don't have very high hash power, and I'm not having much luck with DMD. I'm new to solo mining and don't really understand what I see. I see tentative transactions show up, and they get stuck there. If I restart the software they disappear. Are they stale or orphaned? I also see "Number of transactions: 4", but only two transactions are showing. And that's after having at least 5 blocks accepted according to CGWatcher. So I'm confused.
December 19, 2013, 04:48:15 PM
The new binary simply core dumped at the exception. Here is a backtrace:
(gdb) bt
#0 0x00000000007e78b1 in getframeaddr ()
#1 0x00000000007e67bf in backtrace ()
#2 0x00000000005adb23 in LogStackTrace () at util.cpp:1041
#3 0x000000000041b5d8 in CDataStream::read (this=0x7fffff3f9970,
pch=0x80b505180 "", nSize=) at serialize.h:915
#4 0x000000000044f43b in Unserialize_impl > (is=@0x7fffff3f9970, v=@0x815f2a100,
nType=, nVersion=)
at serialize.h:451
#5 0x00000000004cb93c in Unserialize (is=,
v=, nType=,
nVersion=) at serialize.h:477
#6 0x00000000004da1a2 in Unserialize_impl > (is=@0x7fffff3f9970, v=@0x80b7f81e8, nType=1, nVersion=-1285142016)
at serialize.h:689
#7 0x00000000004db433 in Unserialize_impl > (is=@0x7fffff3f9970, v=@0x7fffff3f9a40, nType=1,
nVersion=) at serialize.h:477
#8 0x0000000000546096 in submitblock (params=,
fHelp=) at serialize.h:477
#9 0x00000000004f6c06 in CRPCTable::execute (this=,
strMethod=, params=@0x7fffff3f9ee8)
at bitcoinrpc.cpp:1046
---Type to continue, or q to quit---
#10 0x0000000000501a86 in ThreadRPCServer3 (parg=0x80a4eb400)
at bitcoinrpc.cpp:992
#11 0x0000000000623e50 in boost::(anonymous namespace)::thread_proxy ()
#12 0x0000000801681210 in pthread_create () from /lib/libthr.so.3
#13 0x00007fffff1fa000 in ?? ()
Cannot access memory at address 0x7fffff3fa000
(gdb)
(gdb) bt
#0 0x00000000007e78b1 in getframeaddr ()
#1 0x00000000007e67bf in backtrace ()
#2 0x00000000005adb23 in LogStackTrace () at util.cpp:1041
#3 0x000000000041b5d8 in CDataStream::read (this=0x7fffff3f9970,
pch=0x80b505180 "", nSize=
#4 0x000000000044f43b in Unserialize_impl
nType=
at serialize.h:451
#5 0x00000000004cb93c in Unserialize
v=
nVersion=
#6 0x00000000004da1a2 in Unserialize_impl
at serialize.h:689
#7 0x00000000004db433 in Unserialize_impl
nVersion=
#8 0x0000000000546096 in submitblock (params=
fHelp=
#9 0x00000000004f6c06 in CRPCTable::execute (this=
strMethod=
at bitcoinrpc.cpp:1046
---Type
#10 0x0000000000501a86 in ThreadRPCServer3 (parg=0x80a4eb400)
at bitcoinrpc.cpp:992
#11 0x0000000000623e50 in boost::(anonymous namespace)::thread_proxy ()
#12 0x0000000801681210 in pthread_create () from /lib/libthr.so.3
#13 0x00007fffff1fa000 in ?? ()
Cannot access memory at address 0x7fffff3fa000
(gdb)
December 19, 2013, 04:12:42 PM
stay tuned please. New client will be released in the next hours.
Thanks. I started mining DMD yesterday and been having trouble with the wallet and network. Trying to sync from start but it's taking ages. I hope the new client helps.
You can always pool mine (there are now three active pools) while you wait. You don't need a client or synchronization for that.
Anyway, as difficulty increases with price, solo mining may not be a very good option soon, unless you have strong hash power.
December 19, 2013, 03:44:33 PM
stay tuned please. New client will be released in the next hours.
Thanks. I started mining DMD yesterday and been having trouble with the wallet and network. Trying to sync from start but it's taking ages. I hope the new client helps.
December 19, 2013, 03:33:09 PM
stay tuned please. New client will be released in the next hours.
December 19, 2013, 03:32:20 PM
I am having weird experience with getting stratum to work with daemondd. The stratum side still reports Internal Server error, yet the daemon from time to time manages to execute AddToWallet. But, sometimes I get this
12/19/13 20:14:40 ThreadRPCServer method=submitblock
12/19/13 20:14:40 keypool return 3
12/19/13 20:14:40
******* exception encountered *******
Can I get some help from developers on this? It seems an internal server error. Since I am running this on FreeBSD and did not find the relevant functions, I commented out the body of the stack trace function like this so it at least compiles.
void LogStackTrace() {
printf("\n\n******* exception encountered *******\n");
if (fileout)
{
#ifndef WIN32
#if 0
void* pszBuffer[32];
size_t size;
size = backtrace(pszBuffer, 32);
backtrace_symbols_fd(pszBuffer, size, fileno(fileout));
#endif
#endif
}
}
So, no stack trace for now..
EDIT: Found the proper library and now have backtrace -- for the next exception.
12/19/13 20:14:40 ThreadRPCServer method=submitblock
12/19/13 20:14:40 keypool return 3
12/19/13 20:14:40
******* exception encountered *******
Can I get some help from developers on this? It seems an internal server error. Since I am running this on FreeBSD and did not find the relevant functions, I commented out the body of the stack trace function like this so it at least compiles.
void LogStackTrace() {
printf("\n\n******* exception encountered *******\n");
if (fileout)
{
#ifndef WIN32
#if 0
void* pszBuffer[32];
size_t size;
size = backtrace(pszBuffer, 32);
backtrace_symbols_fd(pszBuffer, size, fileno(fileout));
#endif
#endif
}
}
So, no stack trace for now..
EDIT: Found the proper library and now have backtrace -- for the next exception.
Jump to: