Julia  |
|
|
|
 i7-4790 can you share the miner ? The link is in OP for both source and pre compiled no there is no compiled cpuminer at the op Oh, you're right I didn't look close enough at screen shot and assumed it was the nearly released ccminer |
|
|
|
i7-4790 can you share the miner ? The link is in OP for both source and pre compiled |
|
|
|
Please don't spam this thread with double/triple quotes. Don't spam! Thank you!
Does it even matter anymore? Once your post has been made/quoted just unwatch the thread and let it be |
|
|
|
still no nvidia gpu miner .. will it be ?
There isn't even an AMD miner yet |
|
|
|
Ok that went faster than expected wallet links in the ANN updated  I've tested the 32 and 64 bit windows installers and the osx wallet. They seem fine so far except for the osx wallet that crashed once in 3 hours due to some networking error on a hackintosh system that is known to have a network driver issue. If you get a warning asking if you want to rebuild the block index (or similar) just click ok and everything should go fine. Again, BACKUP BACKUP BACKUP before you update  thanks! Now the official wallet is faster than this or not? Win32 Binaries https://mega.co.nz/#!1RhATb7b!r3-CqwHjsw-P-nQvPwH0Vn57NXJXDMF9qEBApFdmCpc Win64 Binaries https://mega.co.nz/#!JcolWI6T!e7IBwOwDgTxi2QXTQMZJI-dMEgemIE5D2LyYroUp5PM The only way to know for sure is to test it. What may be faster for one person could be slower for another. Before doing anything make plenty of backups. |
|
|
|
is it a new algo?
Can you read? Algorithm: Scrypt (POW)
|
|
|
|
Hummm dont have active connection on new wallet, do you know what is the problem%? Allowed though Windows Firewall? Yeah!! Debug console addnode 52.24.192.61 69.253.168.73 24.205.47.18 |
|
|
|
Hummm dont have active connection on new wallet, do you know what is the problem%? Allowed though Windows Firewall? |
|
|
|
whywefight don't remember the exact option but in the config file set inttype to string or something along those linesEdit: Abe.conf # Some databases have trouble with the large integers that Abe uses
# for statistics. Setting int-type=str causes Abe to pass certain
# integers to the database as strings and cast them to floating point
# in SQL expressions that calculate statistics. Try this if SQLite
# complains "OverflowError: long too big to convert".
#int-type str |
|
|
|
|
Also selling a sizable quantity PM to make a deal.
|
|
|
|
Add another 1,000,000 DOGED to that bounty Thanks for your tireless effort DogedDev. dogeddev and I think we have it... the chain is processing currently at block 17k got a long ways to go. |
|
|
|
Does doged use a modified coinbase transaction? I tried to manually break down the raw coinbase in the way Electrum does and found where it fails. http://blockexperts.com/doged/tx/3dbf37b079c058a6b9ff7a4b582c6acd4497ea0e8288b46449907f64cb9b6947user@pc:~$ ./dogecoindarkd getrawtransaction 3dbf37b079c058a6b9ff7a4b582c6acd4497ea0e8288b46449907f64cb9b6947
01000000cafb3654010000000000000000000000000000000000000000000000000000000000000000ffffffff0c0230010107062f503253482fffffffff0100d0ed902e000000232103955ef98da45972644d075dc26a0dfcedd44e4f15e4bdea3746472362453fced3ac00000000
Break it down...
01000000 -- version
ca -- varint tx in count (202) This is in all probability wrong also but not where it fails
fb36540100000000000000000000000000000000000000000000000000000000 -- txin prev out hash
00000000 -- txin prev out index
ff -- varint uint64
ffffff0c02300101 -- uint64 (72391854380810239) it proceeds to read 72391854380810239 bytes and fails
07062f503253482fffffffff0100d0ed902e000000232103955ef98da45972644d075dc26a0dfcedd44e4f15e4bdea3746472362453fced3ac00000000 -- doesn't get parsed as it's read in the giant read
However when dogecoindarkd parses it we get
user@pc:~$ ./dogecoindarkd decoderawtransaction 01000000cafb3654010000000000000000000000000000000000000000000000000000000000000000ffffffff0c0230010107062f503253482fffffffff0100d0ed902e000000232103955ef98da45972644d075dc26a0dfcedd44e4f15e4bdea3746472362453fced3ac00000000
{
"txid" : "3dbf37b079c058a6b9ff7a4b582c6acd4497ea0e8288b46449907f64cb9b6947",
"version" : 1,
"time" : 1412889546,
"locktime" : 0,
"vin" : [
{
"coinbase" : "0230010107062f503253482f",
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 200000.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "03955ef98da45972644d075dc26a0dfcedd44e4f15e4bdea3746472362453fced3 OP_CHECKSIG",
"hex" : "2103955ef98da45972644d075dc26a0dfcedd44e4f15e4bdea3746472362453fced3ac",
"reqSigs" : 1,
"type" : "pubkey",
"addresses" : [
"D9T4EAWW6bjpCbEvpXSmUZJEXkeVNZ3j38"
]
}
}
]
}
|
|
|
|
There is no LINUX miner available?
No. But you can install the Windows version on Linux with third party software.By that he means Wine |
|
|
|
Mining with the wallet, per the code in the OP - how can i check to see if it is actually mining?
type to console: gethashespersec you will see it returns you 0h/s It will return 0h/s if you are not mining......if you are mining correctly your wallet "gethashpersec" command will retrieve you the actual hashing speed of your machine. no it will not, using -1 or -2 what ever its not working works only without -x Sorry but this is not true. Wallet built-in miners works perfectly with -1 parameter too. yes there is no problems..  T-INSIDE says -1 works cisahas tests -2 claims it's broken How does that logic follow? |
|
|
|
|
I started poking around a bit and it seems to fail after reading an insanely large number of bytes from the transaction then goes out of bounds on the next read, will keep digging.
|
|
|
|
|
Show Posts
