[ANN] [SHA256]+[CPU] MediterraneanCoin (MED) - REUSE your ERUPTER!!

[zeetak]

What is the process for fixing this issue that I see on my linux wallet?  This transaction was sent probably 2 weeks ago to another wallet that I own (just consolidating MED).

[soulistyce]

What is the process for fixing this issue that I see on my linux wallet?  This transaction was sent probably 2 weeks ago to another wallet that I own (just consolidating MED).

thats what we've been talking about, 0 confirms on large amout transation,
dev is fixing this issue, a new wallet will BE launch to solve it

[zeetak]

What is the process for fixing this issue that I see on my linux wallet?  This transaction was sent probably 2 weeks ago to another wallet that I own (just consolidating MED).

thats what we've been talking about, 0 confirms on large amout transation,
dev is fixing this issue, a new wallet will BE launch to solve it

Ok, great. I am currently trying the py-wallet/rescan method now. I'll report back my findings regardless of the outcome.

Any ETA on that wallet fix?

[battsali]

2 weeks is long long time  

one more important thing i find

people usualy wait 4-5 days to confirm and after that try to delete transaction and

-Wait 48-72 hours so the network can "forget" the transaction (this step is very important!)
-Send the coins again with a fee

You need to wait a few days for the transaction to drop from the memory pool. If you don't wait, the current implementation will treat it as an double spend attempt.




Also if you have a recent backup of your wallet, it would be easier to go back to that than to use pywallet.   

[eestimees]

czfzhifutu and liushui001

please send me your shipping addresses to receive the price you have won on blockhash race!

[namjar]

New bug:

When i change the target of block and wallet file such as C:\Crypto\MED-qt\mediterraneancoin-qt.exe -datadir=C:\Crypto\MED-qt\data -connect=node1.mediterraneancoin.org -connect=node2.mediterraneancoin.org -connect=node3.mediterraneancoin.org -connect=node4.mediterraneancoin.org

Then the problem happened:



I built 2 MED-qt in my one PC, 1 is setting as above, the another is the default setting (%AppData%), when i run the 1 MED-qt, and send med, the problem as the picture, then I run the 2nd (default setting), the wallet file was changed that created a new wallet file (new wallet address and not the backup).

Please fix it in the next version MED-qt

 

[fly757]

What to do , to see in my wallet this 0 confirm ?? to see what's happened

you can try send and accept couple times ,then see what happen later.

for me ,these 0 confirms still stay with now ,actually not care about the MED(about 10MED)

never met this before on another coin's wallet

And I can say ,if the DEV can figure this problem out , I will donate 5'000 MED

And how many active connection do you have usually ?


PS: never mind

usually 8 connections, DEV can go to the wallet which send Bonus for transaction, check the transaction status.

I mean, this problem definitely not my wallet's problem ,it's the problem of Bonus wallet.

so , DEV,please check the Bonus wallet, check all the transactions , you will find some 0 confirms.

[namjar]

one suggestion:

Change the wallet name in the next version MED-qt such as:

English:                   Litecoin - Wallet ==> Mediterraneancoin - Wallet
Simple Chinese:        莱特币 - 钱包 ==> 地中海币 - 钱包
Traditional Chinese:   萊特幣 - 錢包 ==> 地中海幣 - 錢包

[zeetak]

2 weeks is long long time  

one more important thing i find

people usualy wait 4-5 days to confirm and after that try to delete transaction and

-Wait 48-72 hours so the network can "forget" the transaction (this step is very important!)
-Send the coins again with a fee

You need to wait a few days for the transaction to drop from the memory pool. If you don't wait, the current implementation will treat it as an double spend attempt.




Also if you have a recent backup of your wallet, it would be easier to go back to that than to use pywallet.   

Unfortunately, I didn't have a backup copy of my wallet from before the transaction. However, I was able to delete all transactions using the pywallet.py program and then rescan my wallet. All of my coins are now back, safe and sound! Now before I screw them up again, is there a limit to the amount of coins I can send so that this won't happen again?

[tgj121]

2 weeks is long long time 

one more important thing i find

people usualy wait 4-5 days to confirm and after that try to delete transaction and

-Wait 48-72 hours so the network can "forget" the transaction (this step is very important!)
-Send the coins again with a fee

You need to wait a few days for the transaction to drop from the memory pool. If you don't wait, the current implementation will treat it as an double spend attempt.




Also if you have a recent backup of your wallet, it would be easier to go back to that than to use pywallet.   

Unfortunately, I didn't have a backup copy of my wallet from before the transaction. However, I was able to delete all transactions using the pywallet.py program and then rescan my wallet. All of my coins are now back, safe and sound! Now before I screw them up again, is there a limit to the amount of coins I can send so that this won't happen again?

used this way,it's all back after 24 hours,but 0 confirm happen again when I send MED out.

[tgj121]

hi all,
we need to replenish a bit the TRANSACTION BONUS SERVICE!!!

if anybody interested could send some MED to address Mgtq4fJkU5WNH7RedZWunpQHNog84QRXUP it would be really great!!! 

I would donate,but without 0 confirm.waiting for new wallet.

[wzttide]

Market MED/BTC now on index NatSwap on https://www.swaphole.com/

Get more information about SwapHole.com: https://bitcointalk.org/index.php?topic=530080.0

[eestimees]

REMINDER

during next 2.5h ibipot.com MED pool will be offline approx 10 minutes.

[battsali]

REMINDER

during next 2.5h ibipot.com MED pool will be offline approx 10 minutes.

Round Shares Submitted shares since last found block (ie. round shares)
Est. Shares   5,749 (done: 1967.35%)
Pool Valid   113,103
and Time Since Last Block   4 hours 24 minutes 44 seconds
also Confirmed and Unconfirmed not updated but pool accept share

pool work or not ?

[cr1st0f]

REMINDER

during next 2.5h ibipot.com MED pool will be offline approx 10 minutes.

Round Shares Submitted shares since last found block (ie. round shares)
Est. Shares   5,749 (done: 1967.35%)
Pool Valid   113,103
and Time Since Last Block   4 hours 24 minutes 44 seconds
also Confirmed and Unconfirmed not updated but pool accept share

pool work or not ?

The statistics depend on the upgrade script on the server
So don't worry if "stratum" send work to you , all work fine

[battsali]

REMINDER

during next 2.5h ibipot.com MED pool will be offline approx 10 minutes.

Round Shares Submitted shares since last found block (ie. round shares)
Est. Shares   5,749 (done: 1967.35%)
Pool Valid   113,103
and Time Since Last Block   4 hours 24 minutes 44 seconds
also Confirmed and Unconfirmed not updated but pool accept share

pool work or not ?

The statistics depend on the upgrade script on the server
So don't worry if "stratum" send work to you , all work fine

 

i'm thinking this is new BUG 0 confirm from pool

 

[eestimees]

REMINDER

during next 2.5h ibipot.com MED pool will be offline approx 10 minutes.

Round Shares Submitted shares since last found block (ie. round shares)
Est. Shares   5,749 (done: 1967.35%)
Pool Valid   113,103
and Time Since Last Block   4 hours 24 minutes 44 seconds
also Confirmed and Unconfirmed not updated but pool accept share

pool work or not ?

sorry, stats display and share distribution service crashed.. ok running now. Thanks for pointing it out.

It was a total hell today.. I something can go wrong, it will go but all good again now

[battsali]

REMINDER

during next 2.5h ibipot.com MED pool will be offline approx 10 minutes.

Round Shares Submitted shares since last found block (ie. round shares)
Est. Shares   5,749 (done: 1967.35%)
Pool Valid   113,103
and Time Since Last Block   4 hours 24 minutes 44 seconds
also Confirmed and Unconfirmed not updated but pool accept share

pool work or not ?

sorry, stats display and share distribution service crashed.. ok running now. Thanks for pointing it out.

It was a total hell today.. I something can go wrong, it will go but all good again now

some days is terrible and better to stay in bed and don't touch anything   
pool stat is OK now .,., thanks

[battsali]

by the way  FAILOVER strategy work perfect , don't forget to use it 


bfgminer --failover-only -o pool1:port -u pool1workername -p pool1workerpass  -o pool2:port -u pool2workername -p pool2workerpass

[cr1st0f]

Network Stats:


Over 12Ths

Great Job!