While trying to compile dogecoin on my linux machine I've got this error, this is the full output:

$ qmake 
Project MESSAGE: Building with UPNP support
Project MESSAGE: Building with UPNP supportRemoved plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
$ make
cd /home/peach/Programs/dogecoin; /bin/sh share/genbuild.sh /home/peach/Programs/dogecoin/build/build.h
g++ -c -pipe -fstack-protector -O2 -fdiagnostics-show-option -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -D_REENTRANT -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADS
AFE -DBOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN -D__NO_SYSTEM_INCLUDES -DUSE_UPNP=1 -DSTATICLIB -DHAVE_BUILD_INFO -DLINUX -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/s
hare/qt4/mkspecs/linux-g++ -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -Isrc -Isrc/json -Isrc/qt -Ic:/deps -IC:/deps/boost -Ic:/deps/db/build_unix -Ic:/deps/ssl/incl
ude -Ibuild -Ibuild -o build/bitcoin.o src/qt/bitcoin.cpp
In file included from src/main.h:14:0,
                 from src/wallet.h:9,
                 from src/init.h:9,
                 from src/qt/bitcoin.cpp:11:
src/db.h:15:20: fatal error: db_cxx.h: No such file or directory
compilation terminated.
make: *** [build/bitcoin.o] Error 1

trying these commands

getinfo
help

but closed the complete program ..

I've been mining splendidly in Windows using a command line interface with minerd but I cannot herd mine using the Windows Dogecoin-QT app. In Dogecoin-QT I inspected the command created and it appears that there may be an = sign missing, e.g url=stratum+tcp://...... and userpass=XXX....., those = signs were missing in the command line shown in the Dogecoin-QT program.

Updating Dogecoin to use feathercoin over litecoin looks like a viable option to prevent against a 51%?

Versions of dogecoin-qt prior to v13 run fine on OSX 10.6.8. V13, when started, displays a dialog box stating that something is wrong and my choices are to [ignore] or [report] to Apple.

please commit anti multi pool mining patch (aka anti flash mining), all needed changes are public von bitcointalk.org

Please Shibe make icon on right look like one on left for much successes. wow.

http://img594.imageshack.us/img594/3488/14uq.png

many proof. very amaze. such graphic design.

We are seeing a high number of dust (low value) transactions in the Dogecoin network. This causes the blockchain to grow and computing power to be wasted on verifying transactions with no real value (eg 0.0001 DOG)

Bitcoin addressed this via a mandatory fee of a low value. We need to have the servers stop validating low-value transactions.

See: bitcoin/bitcoin#2577

AFAIK, this option has been on the bitcoind daemon since 0.8.2. I don't know why it still isn't in dogecoin.

Error: An error occured while setting up the RPC port xxxx for listening: bind: Cannot assign requested address
root@AY131213154312684966Z:~/coin/dogecoin/src# ./dogecoind
Error: An error occured while setting up the RPC port 25555 for listening: bind: Cannot assign requested address

I've had a lot of switching ports
20000-25000
I am sure that these ports are not occupied

Makefile ignores given parameters and doesn't compile scrypt.c with -fPIC option. WOW just recompiled it manually with gcc scrypt.c -c -o obj/scrypt.o -fPIC but update this WOW makefile

What else is there to say?

dogecoin server was working fine, but one day when I given getinfo command it showed:

$ ~/dogecoind getinfo
{
"version" : 60400,
"protocolversion" : 60003,
"walletversion" : 60000,
"balance" : #####,
"blocks" : 30217,
"connections" : 8,
"proxy" : "",
"difficulty" : 486.17595920,
"testnet" : false,
"keypoololdest" : 1387358219,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : "EXCEPTION: St12out_of_range \nCInv::GetCommand() : type=3 unknown type \ndogecoin in ProcessMessages() \n"
}

the balance #### was censored here by me, rest is pasted exactly.

So it has some exception while trying to read the errors information?

Then I checked in system log, and noticed that grsecurity detected bug (segfault) in bitcoind some time ago:

grsec: From X.X.X.X: Segmentation fault occurred at 0000000000000010 in /home/srv_doge/src/dogecoin/src/dogecoind[dogecoind:19216] uid/euid:1014/1014 gid/egid:1014/1014, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0

the IP (X.X.X.X) was censored here by me.

This was build from sources, and using local libdb 4.8, on Debian 7 with grsecurity kernel on OVH hosting server (dedicated).

Perhaps the original segfault is to blame and then it caused undetermined behaviour of program showing this missleading exception message.

crash on win7 64bit when trying to encrypt wallet. someone on forum also reported this.
other wallets do not crash.

NOTE: Only on certain windows platforms and not on others

Other Manifestations:
Cannot import private key
Cannot run console commands

Such wallet cannot synchronise.

Log keeps repeating:

trying connection 213.73.189.244:22556 lastseen=0.9hrs
connection timeout
trying connection 213.73.189.244:22556 lastseen=0.9hrs
connection timeout

litecoin/feathercoin/bitcoin wallets all work fine.

$ nmap -p 22556 213.73.189.244

Starting Nmap 5.21 ( http://nmap.org ) at 2013-12-18 16:36 WST
Nmap scan report for d549bdf4.cm-10-1a.dynamic.ziggo.nl (213.73.189.244)
Host is up (0.33s latency).
PORT STATE SERVICE
22556/tcp filtered unknown

No... its not my firewall. Tried from two different hosts on two different networks.

I keep seeing debug.log talking about 'bc' as a unit, like this:

WalletUpdateSpent found spent coin 1000.00bc 99fe9b42e190c94fc182b993b5efb7568c15cf294111fc5da482f500e6b3d78e

Shouldn't it be 'dc'? Or better yet, 'DOGE'?

wallet.cpp:
printf("WalletUpdateSpent found spent coin %sbc %s\n", ...);

dogecoin no build on linux

need -mgw46-mt-sd-1_53 remove from LIBS array

linux very much not like c:/ includes

I tried moving 40 million coins from one account to another, but it failed:

$ dogecoind move '' dice 40000000.0001
error: {"code":-3,"message":"Invalid amount"}

Moving it in two lumps of 20 million worked:

$ dogecoind move '' dice 20000000.0001
true
$ dogecoind move '' dice 20000000
true
$ 

I guess there's another limit somewhere that needs increasing.

Also, the fix for the sendtoaddress command only increased the limit from 84M to 500M - that's still not enough. Why not let me send my whole balance at once rather than having to break it into 500M DOGE pieces?

Is there a way to determine what chain a block is in by looking at the raw block data? I know it's possible to do it by back referencing later blocks and checking their previous_block_hash against another block's hash but I am wondering if it's possible to determine through looking at difficulty, bits, or some other piece of data.

I'm not sure what is going on, my pool had 40 workers and 6 MH/s in 36 hours, we haven't received a block! In the dogecoind log it keeps showing orphans. Could that be it?

In my blocks database table it is completely empty.

also, I used the api to get my wallet address, then I copied the server wallet to my pc and the address doesnt even show up under receiving addresses! im puzzled

http://minersareus.com

ERROR: FetchInputs() : 19f5bf501d mempool Tx prev not found dbd6913293
stored orphan tx 19f5bf501d (mapsz 615)
received: inv (37 bytes)
got inventory: tx aba44f64279285d3a757 new
askfor tx aba44f64279285d3a757 0
sending getdata: tx aba44f64279285d3a757
sending: getdata (37 bytes)
received: inv (37 bytes)
got inventory: tx aba44f64279285d3a757 new
askfor tx aba44f64279285d3a757 1387484752000000
sending: inv (37 bytes)
sending: inv (37 bytes)
received: inv (37 bytes)
got inventory: tx 19f5bf501d7cb58a5c55 have
received: addr (31 bytes)
received: inv (73 bytes)
ReplyQuoteNotify

The dogecoin-qt-v13-Mac client crashes every time I open in Mavericks. This is on a late 2008 Macbook Pro, 2.53 GHz Core 2 Duo, with 8 GB 1067 MHz DDR3 memory.

I'm making a block chain viewer, and have been working on a script that imports the block chain into a database as well as performing some calculations on the data. One calculation I perform is determining the chain that the block belongs to - if it's the main chain, a side chain, or a fork (orphan chain).

As the script ran I noticed that at block 15031, the chain starts to generate many side chains. It seemed that on average after block 15031 about every 5-10 blocks a new side chain was being generated. If my script is accurate, then that means that junk data is being filled into the block data file - signifying an attack?

Please see my gist. If my code is accurate, I believe that there is something/someone specifically targetting Dogecoin to make current clients fill their block files with junk data

Can't build on Ubuntu 12.04.

Doge very currency wow! Much blocks = big wallets. Bigger wallets = much wow! Add Proof of Stake blocks to encourage very much more coin. So very energy efficient super green wow!

Setting server=1 in the dogecoin.conf file seems to have no effect on the QT allowing RPC conections. The only way I was able to get the QT client to respond to RPC calls was to start the app like this:

open dogecoin-qt.app --args -server -rpcuser=user -rpcpassword=password

This was my config:

addnode=95.85.29.144
addnode=162.243.113.110
addnode=146.185.181.114
server=1
daemon=1
rpcuser=user
rpcpassword=password

It also will not work if I just use -server this causes it to not read the doge.conf file. Does the client ignore everything in the .conf file if any CLI args are passed to it?

What else is there to say?

I just had a user complaining that he couldn't withdraw. I checked the server logs and saw:

sendtoaddress DR35m6R4Xa2gPVJDBfPcaKGowMUDHL7E7U 15494733.34187310; Error: Error: Transaction creation failed   (code -4)
sendtoaddress DR35m6R4Xa2gPVJDBfPcaKGowMUDHL7E7U 15494731.99990000; Error: Error: Transaction creation failed   (code -4)

I just asked him to try again, and this time it worked:

success: 15476670.44612223 to DR35m6R4Xa2gPVJDBfPcaKGowMUDHL7E7U txid ea9bc97dda49dd36ac0e3fcb539922ec5d5464373d3296e9ecf4a38856ec9068

There was over 80M DOGE in the wallet at the time, so it's not an issue of insufficient funds being available for the transaction.

I searched for 'Transaction creation failed' in the source, and found it only in 2 places: 1) in sendmany() in bitcoinrpc.cpp, which I don't think should be called when running sendtoaddress, and 2) in CWallet::SendMoney() in wallet.cpp. So I guess it's (2) that was being triggered.

There's nothing special about the wallet. I only run it in one place, so it's not a double-spend issue. I have all the private keys available in the wallet, etc. It shouldn't have problems creating transactions.

I've made thousands of calls to sendtoaddress in bitcoind and never seen this error before. I guess it's a bug that has been fixed since the version dogecoin forked.

Is there a chance of using a more up-to-date codebase for dogecoin to avoid such issues?

File /src/net.cpp
Lines 1069, 1096

In miniupnpc v1.5 function UPNP AddPortMapping have more arguments.
You should patch code
from:
port, port, lanaddr, strDesc.c_str(), "TCP", 0);

to:
port, port, lanaddr, strDesc.c_str(), "TCP", 0, "0");

Trying to build on fedora 20. Get an exception when I run dogecoin-qt

A fatal error occured. DogeCoin can no longer continue safely and will quit.

EXCEPTION: 9key_error       
CKey::CKey() : EC_KEY_new_by_curve_name failed       
dogecoin in Runaway exception.

build using:

/usr/lib64/qt4/bin/qmake "USE_UPNP=1"
make

I'm getting this error:

$ dogecoind sendtoaddress D6fBstwziY72FMb5NZJoccmfQ7RBmDfeju 84000001
error: {"code":-3,"message":"Invalid amount"}
$ dogecoind sendtoaddress D6fBstwziY72FMb5NZJoccmfQ7RBmDfeju 84000000
055269d8e4803b6b1ec1604f40609cd3307a415bcaf80374a64f86d35d6aa168
$ 

The problem is with src/bitcoinrpc.cpp:

int64 AmountFromValue(const Value& value)
{
    double dAmount = value.get_real();
    if (dAmount <= 0.0 || dAmount > 84000000.0)
        throw JSONRPCError(-3, "Invalid amount");

The sender address is always unknown in transaction details.

The Mac client 1.4 Alpha 2 crashes upon notification of a transaction. The client appears stable once restarted. Three crash reports are linked below.

Incoming Transaction Crash Report:
http://pastebin.com/uLNyivMN
http://pastebin.com/b6EQZW0F
http://pastebin.com/A9gzTici

I downloaded the new version of the dogecoin-qt wallet version 1.3 and updated the 1.2 version. It crashes all the time during startup. I tried:

• reinstalling the app from scratch
• remove app data from ~/Library/Application Support/ and install app again.

Here is the complete crash report: http://pastebin.com/LyiH6iNf

Using Mac OS X 10.8.5

So not cool.

I would like to set my server as stratum+tcp://.....

but doge adds http:// infront so it becomes http://stratum+tcp://

Dogecoin, please ;;

Linux QT version

many missing
compile on own
such slow
wow

The above image shows a transaction which spends 1M DOGE according to the blockchain, but 2M DOGE according to the client. What's going on here?

$ dogecoind getrawtransaction 7a41006d1b511f875f68707b9f310b1946d7c3e1af6d51961faaf3130d5da4e9
01000000012d5a4ca421230de22ef048d1c2176d8ec71ccd7c212c2d6134d0764c2c74ad2d000000006c493046022100d4d76f87e9edfa770063d86f12d0cf8a915864ee9f857a37e8f22244f405a187022100dcbfca11b1ccdb17e1303519906e7df96604afbb8b0d70a1c65f4a1a39609a6d01210265151f1fc2192e8617f8243e78dab4517a97aaeabcea9e6b446026ac23445884ffffffff0230467c77145e00001976a914303d79d9af56a66108895f36be2a1db805241dfc88ac00407a10f35a00001976a91495d9a9793e162a213d3c9730838f735579a3382688ac00000000
$ dogecoind decoderawtransaction 01000000012d5a4ca421230de22ef048d1c2176d8ec71ccd7c212c2d6134d0764c2c74ad2d000000006c493046022100d4d76f87e9edfa770063d86f12d0cf8a915864ee9f857a37e8f22244f405a187022100dcbfca11b1ccdb17e1303519906e7df96604afbb8b0d70a1c65f4a1a39609a6d01210265151f1fc2192e8617f8243e78dab4517a97aaeabcea9e6b446026ac23445884ffffffff0230467c77145e00001976a914303d79d9af56a66108895f36be2a1db805241dfc88ac00407a10f35a00001976a91495d9a9793e162a213d3c9730838f735579a3382688ac00000000
{
    "txid" : "7a41006d1b511f875f68707b9f310b1946d7c3e1af6d51961faaf3130d5da4e9",
    "version" : 1,
    "locktime" : 0,
    "vin" : [
        {
            "txid" : "2dad742c4c76d034612d2c217ccd1cc78e6d17c2d148f02ee20d2321a44c5a2d",
            "vout" : 0,
            "scriptSig" : {
                "asm" : "3046022100d4d76f87e9edfa770063d86f12d0cf8a915864ee9f857a37e8f22244f405a187022100dcbfca11b1ccdb17e1303519906e7df96604afbb8b0d70a1c65f4a1a39609a6d01 0265151f1fc2192e8617f8243e78dab4517a97aaeabcea9e6b446026ac23445884",
                "hex" : "493046022100d4d76f87e9edfa770063d86f12d0cf8a915864ee9f857a37e8f22244f405a187022100dcbfca11b1ccdb17e1303519906e7df96604afbb8b0d70a1c65f4a1a39609a6d01210265151f1fc2192e8617f8243e78dab4517a97aaeabcea9e6b446026ac23445884"
            },
            "sequence" : 4294967295
        }
    ],
    "vout" : [
        {
            "value" : 1034419.96990000,
            "n" : 0,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 303d79d9af56a66108895f36be2a1db805241dfc OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a914303d79d9af56a66108895f36be2a1db805241dfc88ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "D9YActhMpZ13DVFykFPqzgoycpr3TFuYLq"
                ]
            }
        },
        {
            "value" : 1000000.00000000,
            "n" : 1,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 95d9a9793e162a213d3c9730838f735579a33826 OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a91495d9a9793e162a213d3c9730838f735579a3382688ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "DJoRyGBJHgoqBpEUknxi49RTDLN6MCaVMt"
                ]
            }
        }
    ]
}
$ 

When following doc/readme-qt.rst I was unable to compile due to a header file missing - boost/random/uniform_int_distribution.hpp. I tried running apt-get install libboost-all-dev, but that didn't fix it. Changing to 1.48 fixed it though, using the line below

apt-get install qt4-qmake libqt4-dev build-essential libboost1.48-dev libboost-system1.48-dev \
    libboost-filesystem1.48-dev libboost-program-options1.48-dev libboost-thread1.48-dev \
    libssl-dev libdb++-dev libminiupnpc-dev

Should we try to have all references to dogecoin spelled the same way in the docs? Right now, the C has not made up its mind if it wants to be capitalized or not!

This is not a bug but a feature that others coins have.

As specified in the original bitcoin protocol, generated coins are always credited to the default account. However is convenient that if the payment address belongs to an account, this generated coins should be assigned to that account, as litecoin does nowadays.

It's convenient because otherwise if the user wants to assign an account to it's mined coins it has to be done manually.

By the way, it would be useful to include in the listtransactions rpc method the address involved in each transaction (as newer clients do).

Best regards, minerodepicoypala.

Looking at getBlockValue (and nSubsidy), after the 600 000th block, it will forever be 10k a block. Once it hits 100 billion, it should be set to 0. However, this seems a bit difficult due to the randomness being brought in.

Or rather, that this is intentional? But then the dogecoin thread should mention there is no theoretical cap, but will basically level out at 10 billion (for all intents and purposes)?

Such confuse?

Dogecoin is currently using two different hash functions for block headers - one for proof-of-work, one for inventory and RPC. This is unfortunate, as it means each block is known by two distinct, unrelated identifiers rather than a single unique one - and the identifiers used in the actual p2p protocol itself are useless for proof-of-work verification. Changing this now would require either a hard fork or temporarily supporting getdata and RPC by either hash in newer versions. Nonetheless, the eventual simplicity of just having a single identifier for a block rather than two might justify a transition to scrypt-only.

Whenever the console is opened and importprivkey "(insertprivatekeyhere)" is entered, the client crashes. Although the new address is imported after restarting the client, the crashing is quite a hassle and should not happen.

I've contacted multiple users on reddit and they have all experienced this, so it's not just me personally.

There is an issue where the URL for cpu mining is getting appended to http:// the URL, this means any URL with stratum cannot be configured correctly through client. To fix: remove http:// append to the parameters.

See screenshot:

Hi.

I'm trying to build on debian, it looks like doge depends on libminiupnpc-dev which isn't in the listed dependencies.

Pls update it to 0.8.5 like litecoin is...

The doge hologram

"much security, wow"

Please consider this devs, I propose a revolutionary method of privacy and security for our beloved DOGE.

Secured encrypted balance when wallet is "locked" or in sleep -- Keeps your doges safe from prying eyes.

Real-tiem 3D halograms 👍 These will make you know the person sending you a picture of their balance has the doge to back it up. It would be impossible to duplicate the same hologram, so displaying the balance in front of the (simulated hologram, could just be a rotating gif or something that changes a lot randomly.) so that if someone screencaps it, would increase difficulty to scam people, if you could quickly show proof how you are a legit dogeillionaire and not some one who is riding the bandwagon.

Thanks for reading my proposal for increased dogecoin security. Perhaps if we are such revolutionary, that other coins copy us for innovations.