Someone is throwing some hashes on the network:
{
"blocks" : 95373,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"netmhashps" : 24.59423428,
"netstakeweight" : 1435846358694684.75000000,
"errors" : "",
"pooledtx" : 0,
}
"netmhashps" : 51.12721954,
"netmhashps" : 96.57597589
"netmhashps" : 122.61632633,
"netmhashps" : 149.41247007,
etc.
Whoever it is, is getting a lot of 5 MOJO blocks ?? Very expensive MOJO I say...
Topic: [MOJO] MOJOv3 has been taken over by new devs - page 38. (Read 167299 times)
Dev please check the link to Windows walllet 2.3 on OP. I am getting this error:
" Error (404)
We can't find the page you're looking for. "
" Error (404)
We can't find the page you're looking for. "
Apologies, all the links have been updated now. I just moved everything to Mega. Should work now
for the love of everything that is good...stop using mega (and other file sharing websites) to distribute pre-compiled binaries of open source code. Github has a very viable means of hosting compiled source. learn it, use it, love it.
Ok, I'll look into that
EDIT: I have moved the binaries to GitHub as it does seem reasonable to have it all in one place...new links in the OP.
Dev please check the link to Windows walllet 2.3 on OP. I am getting this error:
" Error (404)
We can't find the page you're looking for. "
" Error (404)
We can't find the page you're looking for. "
Apologies, all the links have been updated now. I just moved everything to Mega. Should work now
for the love of everything that is good...stop using mega (and other file sharing websites) to distribute pre-compiled binaries of open source code. Github has a very viable means of hosting compiled source. learn it, use it, love it.
Dev please check the link to Windows walllet 2.3 on OP. I am getting this error:
" Error (404)
We can't find the page you're looking for. "
" Error (404)
We can't find the page you're looking for. "
Apologies, all the links have been updated now. I just moved everything to Mega. Should work now
Dev please check the link to Windows walllet 2.3 on OP. I am getting this error:
" Error (404)
We can't find the page you're looking for. "
" Error (404)
We can't find the page you're looking for. "
Question:
Why I can't see unconfirmed transactions in the block explorer?
Why I can't see unconfirmed transactions in the block explorer?
I will have a look at it.
I have noticed that sometimes when I make a tx, it will not be confirmed unless I stake a block and sometimes when I make a tx, although my wallet is locked I get a PoS block. This is on the fix list for the next release.
EDIT: I have started to detail the know bugs in v.2.3 (probably from earlier versions) in the ROAD MAP (known bugs in v.2.3) list.
If you find 'bugs' the best thing to do is to post a description of the problem in this thread and also send an e-mail to bugs-at-mojocoin.org / PM me so that I am aware of it and I will try to get all the deatils in the Road Map bug list to be considered for the next release.
Question:
Why I can't see unconfirmed transactions in the block explorer?
Why I can't see unconfirmed transactions in the block explorer?
Here some examples for very small transactions which were not accepted by the network.
I paied a higher fee of 0.01 MOJO/kB.
edit: all times are UTC+2
5 inputs, 818 bytes:
4 inputs, 670 bytes
3 inputs, 522 bytes
2 inputs, 374 bytes
1 inputs, 226 bytes
I paied a higher fee of 0.01 MOJO/kB.
edit: all times are UTC+2
5 inputs, 818 bytes:
Code:
Status: 0/unconfirmed, broadcast through 9 nodes
Date: 28.08.2016 11:19
To: stakeMN4 MAgq8vsZEvQrNLP5dHoLzH9j3YYsXXbn7u
Debit: -138.39 MOJO
Transaction fee: -0.01 MOJO
Net amount: -138.40 MOJO
Transaction ID: e827dee4819f9951afb76ca9a6251c5d9c49440056239429c6fa4b84fd91b397-000
Date: 28.08.2016 11:19
To: stakeMN4 MAgq8vsZEvQrNLP5dHoLzH9j3YYsXXbn7u
Debit: -138.39 MOJO
Transaction fee: -0.01 MOJO
Net amount: -138.40 MOJO
Transaction ID: e827dee4819f9951afb76ca9a6251c5d9c49440056239429c6fa4b84fd91b397-000
4 inputs, 670 bytes
Code:
Status: 0/unconfirmed, broadcast through 9 nodes
Date: 28.08.2016 11:20
To: stakeMN4 MAgq8vsZEvQrNLP5dHoLzH9j3YYsXXbn7u
Debit: -93.69 MOJO
Transaction fee: -0.01 MOJO
Net amount: -93.70 MOJO
Transaction ID: bdceaabe56ba4e02ac2660ec4680b853952fb0f791914c72bd82ff0c75aab639-000
Date: 28.08.2016 11:20
To: stakeMN4 MAgq8vsZEvQrNLP5dHoLzH9j3YYsXXbn7u
Debit: -93.69 MOJO
Transaction fee: -0.01 MOJO
Net amount: -93.70 MOJO
Transaction ID: bdceaabe56ba4e02ac2660ec4680b853952fb0f791914c72bd82ff0c75aab639-000
3 inputs, 522 bytes
Code:
Status: 0/unconfirmed, broadcast through 9 nodes
Date: 28.08.2016 11:22
To: stakeMN4 MAgq8vsZEvQrNLP5dHoLzH9j3YYsXXbn7u
Debit: -18.09 MOJO
Transaction fee: -0.01 MOJO
Net amount: -18.10 MOJO
Transaction ID: f458d5daf8e3c9e032de99324afd546a55006ec688f3d04ab60a32322a83d5f5-000
Date: 28.08.2016 11:22
To: stakeMN4 MAgq8vsZEvQrNLP5dHoLzH9j3YYsXXbn7u
Debit: -18.09 MOJO
Transaction fee: -0.01 MOJO
Net amount: -18.10 MOJO
Transaction ID: f458d5daf8e3c9e032de99324afd546a55006ec688f3d04ab60a32322a83d5f5-000
2 inputs, 374 bytes
Code:
Status: 0/unconfirmed, broadcast through 9 nodes
Date: 28.08.2016 11:23
To: stakeMN4 MAgq8vsZEvQrNLP5dHoLzH9j3YYsXXbn7u
Debit: -10.29 MOJO
Transaction fee: -0.01 MOJO
Net amount: -10.30 MOJO
Transaction ID: 923e871c8c3793afc6824c57f857bf446fee5bee3b23a4bc961f6d5d30c68a16-000
Date: 28.08.2016 11:23
To: stakeMN4 MAgq8vsZEvQrNLP5dHoLzH9j3YYsXXbn7u
Debit: -10.29 MOJO
Transaction fee: -0.01 MOJO
Net amount: -10.30 MOJO
Transaction ID: 923e871c8c3793afc6824c57f857bf446fee5bee3b23a4bc961f6d5d30c68a16-000
1 inputs, 226 bytes
Code:
Status: 0/unconfirmed, broadcast through 9 nodes
Date: 28.08.2016 11:24
To: stakeMN4 MAgq8vsZEvQrNLP5dHoLzH9j3YYsXXbn7u
Debit: -4.59 MOJO
Transaction fee: -0.01 MOJO
Net amount: -4.60 MOJO
Transaction ID: f49ef92d6c0f4a2905cafd64ec109c24837288775f305253e156ee8227cb4553-000
Date: 28.08.2016 11:24
To: stakeMN4 MAgq8vsZEvQrNLP5dHoLzH9j3YYsXXbn7u
Debit: -4.59 MOJO
Transaction fee: -0.01 MOJO
Net amount: -4.60 MOJO
Transaction ID: f49ef92d6c0f4a2905cafd64ec109c24837288775f305253e156ee8227cb4553-000
i tried to reunite on a single address via a payment to myself 7 mined blocks for a total of 40 MOJO the tx size was small 1582 byte with a tx fee of 0.002 but the tx wasn't included in any new block until i mined a new PoW block.
i just noticed on the macwallet at least, the custom change address in the send tab does not work
just goes to random change address, seemingly as if one never clicked the box ..
am testing another similar wallet to see if it's mojo specific or not. but it won't bloody send anything . lol
ok. ExclusiveCoin (another transfer clone) has same problem it seems.
I'm aware of a few minor issues and I am compiling a list of seemingly GUI related bugs and will try to get these things fixed in the next release.
i just noticed on the macwallet at least, the custom change address in the send tab does not work
just goes to random change address, seemingly as if one never clicked the box ..
am testing another similar wallet to see if it's mojo specific or not. but it won't bloody send anything . lol
ok. ExclusiveCoin (another transfer clone) has same problem it seems.
Trade [MOJO] MojoCoin with MegaCrypton.com Secured Crypto trade Platform.
Recently we deployed into more featured and secured platform.
BTC: https://live.megacrypton.com/market/66
LTC: https://live.megacrypton.com/market/67
Megacrypton MOJO WebWallet: https://live.megacrypton.com/login
Megacrypton MOJO BlockExplorer: http://blockchain.megacrypton.com/mojo/
SIGNUP FOR MEGACRYPTON: https://live.megacrypton.com/user/register
Twitter: https://twitter.com/megacrypton
Facebook: https://www.facebook.com/Megacrypton-1048724951862655
Official Thread: https://bitcointalksearch.org/topic/megacryptoncom-trusted-secure-crypto-trading-platform-1565600
Recently we deployed into more featured and secured platform.
BTC: https://live.megacrypton.com/market/66
LTC: https://live.megacrypton.com/market/67
Megacrypton MOJO WebWallet: https://live.megacrypton.com/login
Megacrypton MOJO BlockExplorer: http://blockchain.megacrypton.com/mojo/
SIGNUP FOR MEGACRYPTON: https://live.megacrypton.com/user/register
Twitter: https://twitter.com/megacrypton
Facebook: https://www.facebook.com/Megacrypton-1048724951862655
Official Thread: https://bitcointalksearch.org/topic/megacryptoncom-trusted-secure-crypto-trading-platform-1565600
Nice Exchange ^^
Trade [MOJO] MojoCoin with MegaCrypton.com Secured Crypto trade Platform.
Recently we deployed into more featured and secured platform.
BTC: https://live.megacrypton.com/market/66
LTC: https://live.megacrypton.com/market/67
Megacrypton MOJO WebWallet: https://live.megacrypton.com/login
Megacrypton MOJO BlockExplorer: http://blockchain.megacrypton.com/mojo/
SIGNUP FOR MEGACRYPTON: https://live.megacrypton.com/user/register
Twitter: https://twitter.com/megacrypton
Facebook: https://www.facebook.com/Megacrypton-1048724951862655
Official Thread: https://bitcointalksearch.org/topic/megacryptoncom-trusted-secure-crypto-trading-platform-1565600
Recently we deployed into more featured and secured platform.
BTC: https://live.megacrypton.com/market/66
LTC: https://live.megacrypton.com/market/67
Megacrypton MOJO WebWallet: https://live.megacrypton.com/login
Megacrypton MOJO BlockExplorer: http://blockchain.megacrypton.com/mojo/
SIGNUP FOR MEGACRYPTON: https://live.megacrypton.com/user/register
Twitter: https://twitter.com/megacrypton
Facebook: https://www.facebook.com/Megacrypton-1048724951862655
Official Thread: https://bitcointalksearch.org/topic/megacryptoncom-trusted-secure-crypto-trading-platform-1565600
Does anyone else's mojocoind keep crashing a few seconds after launching in Windows? I can't get it to run.
we need to ask to coinmarketcap.com to remove yobit
!!NEW!! - EXCHANGE
I am happy to announce that MOJO is now listed at NovaExchange with a BTC trading pair - >> LINK <<
It is a small exchange but it will help to spread the MOJO!!!
I am happy to announce that MOJO is now listed at NovaExchange with a BTC trading pair - >> LINK <<
It is a small exchange but it will help to spread the MOJO!!!
Good news! the more exchange the better.
!!NEW!! - EXCHANGE
I am happy to announce that MOJO is now listed at NovaExchange with a BTC trading pair - >> LINK <<
It is a small exchange but it will help to spread the MOJO!!!
I am happy to announce that MOJO is now listed at NovaExchange with a BTC trading pair - >> LINK <<
It is a small exchange but it will help to spread the MOJO!!!
Any idea why a payment to myself would get stuck in unconfirmed status?
It could be that the transaction size is to big. You should use 'coin control' and you can see the transaction size and if it is over the limit.
No, It was just moving coins from one MN address to a new address. I had an issue with it restarting. Now I can't access those funds. The repairwallet command doesn't help either. How do I regain access to these funds?
If the tx remains unconfirmed it should be rejected after a while and a rescan should resolve it. I don't know how long it might take for the tx to be rejected. I will look into it.
The best way is to replace the wallet.dat file with an older version (from the time before the transaction) and do a "repairwallet" from debug console.
If you have no backuped wallet, see Menu "Settings|Show Autobackup"
Rescan will help you to get back the coins from failed transactions. You also need to do repairwallet after that. Then restart thewallet.
Another option is to dump the private key/s of the old wallet to a new wallet.dat without the need to repair the wallet.
I will add in three until four weeks the command -zapwallettxes. That is then better.
Any idea why a payment to myself would get stuck in unconfirmed status?
It could be that the transaction size is to big. You should use 'coin control' and you can see the transaction size and if it is over the limit.
No, It was just moving coins from one MN address to a new address. I had an issue with it restarting. Now I can't access those funds. The repairwallet command doesn't help either. How do I regain access to these funds?
If the tx remains unconfirmed it should be rejected after a while and a rescan should resolve it. I don't know how long it might take for the tx to be rejected. I will look into it.
The best way is to replace the wallet.dat file with an older version (from the time before the transaction) and do a "repairwallet" from debug console.
If you have no backuped wallet, see Menu "Settings|Show Autobackup"
Rescan will help you to get back the coins from failed transactions. You also need to do repairwallet after that. Then restart thewallet.
Another option is to dump the private key/s of the old wallet to a new wallet.dat without the need to repair the wallet.
Any idea why a payment to myself would get stuck in unconfirmed status?
It could be that the transaction size is to big. You should use 'coin control' and you can see the transaction size and if it is over the limit.
No, It was just moving coins from one MN address to a new address. I had an issue with it restarting. Now I can't access those funds. The repairwallet command doesn't help either. How do I regain access to these funds?
If the tx remains unconfirmed it should be rejected after a while and a rescan should resolve it. I don't know how long it might take for the tx to be rejected. I will look into it.
The best way is to replace the wallet.dat file with an older version (from the time before the transaction) and do a "repairwallet" from debug console.
If you have no backuped wallet, see Menu "Settings|Show Autobackup"
Rescan will help you to get back the coins from failed transactions. You also need to do repairwallet after that. Then restart thewallet.
Jump to: