please confirm that your sends of 100 and 94 worked.
Nope, my 1,000 and 94 payment did not register. Must be something with the 1.0.8 client, but switching back to 1.0.7 did not change anything. Payments seem to register in the client but not on the network (0 confirmations, no show in block explorer). All my payments with the experimental Windows client back to (including) 26 December are not visible in the block explorer. Something is going wrong.

{
"amount" : -1000.00000000,
"fee" : -1.00000000,
"confirmations" : 0,
"txid" : "f0fcc2e92f93fb26e508d305a82fa0274d61fcbb2737d3e39c44533bf5fa0020",
"time" : 1388257696,
"timereceived" : 1388257696,
"details" : [
{
"account" : "",
"address" : "1Md25acfmv3ifWoE25fMDMz96z5pCvi46D",
"category" : "send",
"amount" : -1000.00000000,
"fee" : -1.00000000
}
]
}

{
"amount" : -1000.00000000,
"fee" : -1.00000000,
"confirmations" : 0,
"txid" : "f0fcc2e92f93fb26e508d305a82fa0274d61fcbb2737d3e39c44533bf5fa0020",
"time" : 1388257696,
"timereceived" : 1388257696,
"details" : [
{
"account" : "",
"address" : "1Md25acfmv3ifWoE25fMDMz96z5pCvi46D",
"category" : "send",
"amount" : -1000.00000000,
"fee" : -1.00000000
}
]
}
Do you have an old version of the Windows client for me (let's say: 1.0.3)? |
|
|
|
Sent 1,000 DVC from 1.0.8 Windows client to Vircurex. Not shown in the block explorer yet. Sent 94 DVC (triggered 6 DVC payment fee) to my (older) Linux wallet. Not shown in the block explorer yet. No sign yet of your 1,000 into here (my Linux wallet). It seems we both cannot get the 1.0.8 client to register payments into the network. |
|
|
|
Waiting for rptiela's $350 and lower....  |
|
|
|
multipool.us is not working ? or does it not display the eranings since 3 hours ?
Switched to other pool due to unstable connection. |
|
|
|
But for some reason when i send coins to vircurex (old client)
my transaction doesnt get accepted I think? Id like someone else to try or give me
their address while using old client so I cam try sending u coins.
This is my Linux client: 1NtbgQ61TH579orJQEpAZ4zGvgyzLX4L39 I had some payments disappear in the black hole as well. Those were payments from the Linux client to Cryptostocks.com. One went through some hours after the payment, the other after some days. The client showed the payment but the online block explorers did not state a payment having been made. In the end, things were settled over time. |
|
|
|
Long story short, ... im just in zombie mode.
Now, just get out of zombie mode. There is opportunity every single day. And this crypto thing is just about to get started.... It's easy looking back. Looking forward, is was extremely uncomfortable buying Bitcoins via an escrow site with person-2-person bank transfers, not to forget the long dwindle from $32 to $1.98..... You, Sir, are a victim of captain Hindsight.  |
|
|
|
You should get some Dogecoins for this  |
|
|
|
|
Ok, tested the payment fees again. When sending 8 DVC, no message from my client (it sends the payment right away). At 7 DVC, the client informs me that a 1.2 DVC fee will apply. I have not investigated further into decimals.
|
|
|
|
this shit makes me sick. i left the scene because this is all a sad joke. ... I've been here before.. ... PS: i made faaar more than that AND did it with credibility and class and integrity.. something you guys can NOT claim  Guess this sums it up. |
|
|
|
|
It does not punish a payment of 1 DVC (payment fee is 0.2 DVC).
|
|
|
|
Any news about a Android Dogecoin wallet yet?
This is vital. A Doge coin wallet on Android/whatever mobile phone with a light weight block chain. Something like Mycelium. Mobile will be everything the next few years. Crypto currency is perfect for this environment. |
|
|
|
|
Updated to 1.0.6 (v0.8.5.1-g25a7d46-beta). Still got the 6 DVC payment fee message.
Therefore, I threw away the block chain files (except wallet.dat of course) and synched again. Still the same problem.
Then I thought of installing the 32 bit wallet instead of the 64 bit I installed each time. Voila, I can send 10 DVC with a 0.20 DVC fee.
A 1 DVC payment also takes only 0.2 DVC fee instead of 1.2 DVC fee.
I will remain with the 32 bit version for now.
|
|
|
|
|
I think the basic argument is whether falling prices cause people to postpone purchase of items. I think that in general this is a fallacy. Regardless whether electronics is the best example and whether this can be compared to a deflating currency, I do not believe in the concept of people postponing purchase forever. Now is more valuable than next year. We humans all face an equal and rock solid constraint: time.
|
|
|
|
Go read the archives. You will see what he really thinks (and he was a pretty lousy investor too).
I know what he thinks and he has been right about 8 years in a row already. The Big Picture, not investments. |
|
|
|
So on transaction5 which you stated you were sending 10
dvc to weisoq for 6 dvc fee.. I see 10 going to weisoq but you transferred out 2145 not 16?
If I understand the workings of the Bitcoin protocol sufficient, the payment caused my 2145 DVC in the wallet to be split into 2129 (remaining) DVC and 16 DVC outgoing, of which 10 DVC was the actual payment. The new address for the 2129 that stay in my wallet remains hidden from me. I don't have the 1.0.1 version anymore to test the older version. |
|
|
|
I have to strongly question the intelligence of the author of that article
I think you should read up on his blog posts from 2005 until now and ask yourself that question again. The guy is total common sense. Not that he is fault free, but he surely is intelligent. |
|
|
|
why the fucking dogecoin, can not encryt wallet with pass?
every time i encrypt it with pass, it will crash in windows. and i checked forum, seems no solution. OMG!!!!!!
doge want to die quickly? !!!! solve the security problem first.
i lost some K in online wallet.
Why do you want to be the example of unnessesary rudeness? I saw posts that running the wallet in XP legacy mode may fix the set password crash. Have not tried it myself. |
|
|
|
The connection between 'millions' and 'mine yourself' is irresistable. |
|
|
|
It seems my posts give rise to some confusion, so here's a recap. On 22 December 2013, I installed the experimental Windows client for testing purposes. This was a completely new fresh wallet on this PC. This was version v0.8.5.1-g25a7d46-beta. Below is a list of the transactions. 22 December 2013Transaction 01 : incoming 10 DVCWeisoq made a payment to me to test the wallet. Transaction 02 : outgoing 10 DVCPaying 10 DVC back to Weisoq went ok with a 0.5 DVC fee. Weisoq thus got 9.5 DVC back because I had no more than 10 DVC in the wallet. I made a post about this client at Devtome here25 December 2013Installed the 1.0.3 client v0.8.5.1-g25a7d46-beta. Transaction 03 : incoming 10 DVCWeisoq again paid 10 DVC into my wallet. Transaction 04 : incoming 2000+ DVCSubsequently, upon wanting to return the amount, I encountered the fee issue (not 0.5 DVC but 5.5-6 DVC), see post here. I held off the repayment while the update to 1.0.4 was being prepared. To prepare to reimburse Weisoq in full, I put some Devcoins from other sources into the wallet (2000+). Transaction 05 : outgoing 16 DVCI updated the client to 1.0.4 and still encountered the 6 DVC payment fee. I sent 10 DVC to Weisoq with a 6 DVC fee. 26 December 2013I updated the client to 1.0.5 and still got the message that a 10 DVC payment involves 6 DVC payment fee. See post hereTransaction 06 : outgoing 1000 DVCTo support the Devcoin Payment Block CountdownHope that clarifies things. |
|
|
|
|
Show Posts
