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
Topic: [ANN] [SHA256]+[CPU] MediterraneanCoin (MED) - REUSE your ERUPTER!! - page 47. (Read 227781 times)
April 04, 2014, 01:23:12 PM
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
April 04, 2014, 01:18:45 PM
REMINDER
during next 2.5h ibipot.com MED pool will be offline approx 10 minutes.
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
April 04, 2014, 12:49:24 PM
REMINDER
during next 2.5h ibipot.com MED pool will be offline approx 10 minutes.
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 April 04, 2014, 12:43:08 PM
REMINDER
during next 2.5h ibipot.com MED pool will be offline approx 10 minutes.
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
April 04, 2014, 12:39:11 PM
REMINDER
during next 2.5h ibipot.com MED pool will be offline approx 10 minutes.
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
April 04, 2014, 12:25:58 PM
REMINDER
during next 2.5h ibipot.com MED pool will be offline approx 10 minutes.
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 ?
April 04, 2014, 06:52:28 AM
REMINDER
during next 2.5h ibipot.com MED pool will be offline approx 10 minutes.
during next 2.5h ibipot.com MED pool will be offline approx 10 minutes.
April 04, 2014, 03:53:50 AM
Market MED/BTC now on index NatSwap on https://www.swaphole.com/
Get more information about SwapHole.com: https://bitcointalksearch.org/topic/exchange-swapholecom-trailing-stop-2fa-live-cryptsy-trades-graph-530080
Get more information about SwapHole.com: https://bitcointalksearch.org/topic/exchange-swapholecom-trailing-stop-2fa-live-cryptsy-trades-graph-530080
April 04, 2014, 01:46:33 AM
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!!!
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.
April 04, 2014, 01:16:43 AM
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.
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.
April 03, 2014, 10:59:15 PM
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.
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?
April 03, 2014, 09:06:14 PM
one suggestion:
Change the wallet name in the next version MED-qt such as:
English: Litecoin - Wallet ==> Mediterraneancoin - Wallet
Simple Chinese: 莱特币 - 钱包 ==> 地中海币 - 钱包
Traditional Chinese: 萊特幣 - 錢包 ==> 地中海幣 - 錢包
Change the wallet name in the next version MED-qt such as:
English: Litecoin - Wallet ==> Mediterraneancoin - Wallet
Simple Chinese: 莱特币 - 钱包 ==> 地中海币 - 钱包
Traditional Chinese: 萊特幣 - 錢包 ==> 地中海幣 - 錢包
April 03, 2014, 08:46:57 PM
What to do , to see in my wallet this 0 confirm ?? to see what's happened
?? 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.
April 03, 2014, 08:25:07 PM
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
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
April 03, 2014, 01:50:22 AM
czfzhifutu and liushui001
please send me your shipping addresses to receive the price you have won on blockhash race!
please send me your shipping addresses to receive the price you have won on blockhash race!
April 02, 2014, 12:04:27 PM
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.
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.
April 02, 2014, 11:40:19 AM
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?
April 02, 2014, 11:19:15 AM
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
April 02, 2014, 10:54:11 AM
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).
April 02, 2014, 10:52:48 AM
hi all,
after castiel_koo issue, we are working on a modification of the wallet and daemon so that the network can accept larger transactions (NOT in MED value, but in KByte SIZE), the modification is already on github (https://github.com/mrtexaznl/mediterraneancoin),
in a couple of days we will release a Windows build, in the meanwhile linux users that build from source can pull from git the latest updates and rebuild their images.
thanx!!!
after castiel_koo issue, we are working on a modification of the wallet and daemon so that the network can accept larger transactions (NOT in MED value, but in KByte SIZE), the modification is already on github (https://github.com/mrtexaznl/mediterraneancoin),
in a couple of days we will release a Windows build, in the meanwhile linux users that build from source can pull from git the latest updates and rebuild their images.
thanx!!!
Great to here that,i really hope that could solute this issue,becasue not just me suffer from it
Thanks for the Dev closely follow!
You write , like all we must know for your issue
i can't find post from you for some kind of issue you talk
could you explain what issue you have
0 confirm or what efficient
I meet the zero confirm problem and had been try all the ways you guy provide but seem didnt work.
I hadnt post in public cause i just PM the Dev which i thought that migth be the most efficient way
mmm now we know for what you talk, and new version must fix that Ok thanks
i try a lot of transactions but ,.,.,. successful
i can't see this zero confirmand for export,import privkey and pywallet method for sure work for other altcoin and for bitcoin also, when this happened accidentally but seems MED case is different
i just try to help
i think also 0 confirm is related and with other
The network will either accept your transaction eventually and the coins will be spent OR it will drop the transaction and the coins won't be spent. However, if you delete the transaction from your wallet and spend the same inputs again on a new transaction, the miners might see a double-spend and reject that one, too.
Best thing is just to wait it out. or wait to dev to fix it
i'm just interested why i can't take 0 confirm transactions in my wallet .,.,.,.,.,.,.,.
Jump to: