Topic: [ANN][MIN] Minerals - POS | Developing own anon solution | - page 11. (Read 742197 times)
I love Minerals!! great work Hoshimaru !!
Hello everyone,
i'm from usecryptos.com
we will add Minerals to the exchange as soon as the new wallet is ready.
Regards
Hi snakegii'm from usecryptos.com
we will add Minerals to the exchange as soon as the new wallet is ready.
Regards
That's awesome! We're working on getting the wallet back on track. Trading on mobile platform? Why didn't I noticed the existance of usecryptos.com before?
I was already happy when I found out about Bitfinex to get away from Kraken's new fees :pAnyway: work is being done, still tonight ^^
Doing some research about ECDSA key pairs (left) and building another release of miniupnpc for Windows (right).
I just takes time. The past few days have been insane. I basically took a week off from work, and ended building a veranda with my dad at the parent's place. Now that's a totally different kind of building stuff
glad to see this coin and idea is still being brought back from the dead. Great job, guys!
(^_^)b
glad to see this coin and idea is still being brought back from the dead. Great job, guys!
Hello everyone,
i'm from usecryptos.com
we will add Minerals to the exchange as soon as the new wallet is ready.
Regards
i'm from usecryptos.com
we will add Minerals to the exchange as soon as the new wallet is ready.
Regards
At the moment working on getting the wallet working on all platforms with QT5 iso QT4.
For Windows, it's OK. For Linux too, but you have to compile it yourself. Looking into building a statically linked version if possible, avoiding to download many of the dependencies. And of course, an OS X version. That last one is going to be harder as I've never touched that platform before.
Test transactions between old and new version worked:
Old > New: http://explorer.morningminerals.com/tx/f9efad85ec85adeba2bd24a3e5ea042f58b858c8920541916bd81d003e62b026
New > Old: http://explorer.morningminerals.com/tx/8f6dbead3c88cf671b7ad13b5adddf5c2c4309b138055ac89da6bc7fefd9cdce
For Windows, it's OK. For Linux too, but you have to compile it yourself. Looking into building a statically linked version if possible, avoiding to download many of the dependencies. And of course, an OS X version. That last one is going to be harder as I've never touched that platform before.
Test transactions between old and new version worked:
Old > New: http://explorer.morningminerals.com/tx/f9efad85ec85adeba2bd24a3e5ea042f58b858c8920541916bd81d003e62b026
New > Old: http://explorer.morningminerals.com/tx/8f6dbead3c88cf671b7ad13b5adddf5c2c4309b138055ac89da6bc7fefd9cdce
Hello..
was not here long time. I see Hoshimaru is doing some crazy stuff but may i ask what is future plan for minerals?
was not here long time. I see Hoshimaru is doing some crazy stuff but may i ask what is future plan for minerals?
thanks for the Hard work..
Another small update:
UPNP is enabled
This will need some testing, but so far it seems to be working. Wallet gets 6 connections in no time after starting the wallet.
I'll be modifying some of the icons and images. Basically reverting to the original bitcoin-core icon, except for the Minerals logo of course. Minerals-dev used very bright and white icons and graphics on his dark theme, but they are not very visible in the "stripped" version.
But first of all... getting an introduced to the QT toolset. It's not a matter of overwriting image files. It's more subtle :p
UPNP is enabled
This will need some testing, but so far it seems to be working. Wallet gets 6 connections in no time after starting the wallet.
I'll be modifying some of the icons and images. Basically reverting to the original bitcoin-core icon, except for the Minerals logo of course. Minerals-dev used very bright and white icons and graphics on his dark theme, but they are not very visible in the "stripped" version.
But first of all... getting an introduced to the QT toolset. It's not a matter of overwriting image files. It's more subtle :p
Another small update:
UPNP is enabled
This will need some testing, but so far it seems to be working. Wallet gets 6 connections in no time after starting the wallet.
I'll be modifying some of the icons and images. Basically reverting to the original bitcoin-core icon, except for the Minerals logo of course. Minerals-dev used very bright and white icons and graphics on his dark theme, but they are not very visible in the "stripped" version.
But first of all... getting an introduced to the QT toolset. It's not a matter of overwriting image files. It's more subtle :p
UPNP is enabled
This will need some testing, but so far it seems to be working. Wallet gets 6 connections in no time after starting the wallet.
I'll be modifying some of the icons and images. Basically reverting to the original bitcoin-core icon, except for the Minerals logo of course. Minerals-dev used very bright and white icons and graphics on his dark theme, but they are not very visible in the "stripped" version.
But first of all... getting an introduced to the QT toolset. It's not a matter of overwriting image files. It's more subtle :p
A sneak preview
QT Wallet
Headless Wallet being queried
It's undergoing some additional testing. We don't want to lose Minerals to the void, right?
QT Wallet
Headless Wallet being queried
It's undergoing some additional testing. We don't want to lose Minerals to the void, right?
Hey Hoshimaru,
I just really want to give you props for your dedication. I have big respect for you!
Doge
A sneak preview
QT Wallet
Headless Wallet being queried
It's undergoing some additional testing. We don't want to lose Minerals to the void, right?
QT Wallet
Headless Wallet being queried
It's undergoing some additional testing. We don't want to lose Minerals to the void, right?
In the meantime the headless Mineralsd.exe wallet is working like a charm. Will be working on QT and miniupnpc now. Hopefully I can get it done this weekend, but no promises: Murphy can still hit me with its stick 
http://www.morningminerals.com/?p=580
http://www.morningminerals.com/?p=580
For the next days I'm going to have some investigation/debugging/fixing to do. Building the headless Windows wallet succeeded, but I get this "Assertion failed" error when running it. The good news is that it connects to the DNS seeds and receives a list of clients, although not that many at this moment.
And the debug.log
We need to fix this first, because it will also affect the QT wallet. The fixes and workaround presented in various bitcointalk topics for people facing that crash in other PoS wallets did not help.
Code:
C:\Minerals\New>Mineralsd.exe
Assertion failed: pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGe
nesisBlock : hashGenesisBlockTestNet), file kernel.cpp, line 372
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
C:\Minerals\New>
Assertion failed: pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGe
nesisBlock : hashGenesisBlockTestNet), file kernel.cpp, line 372
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
C:\Minerals\New>
And the debug.log
Code:
Minerals version v1.0.0.0 ()
Using OpenSSL version OpenSSL 1.0.1j 15 Oct 2014
Startup time: 11/09/14 13:59:55
Default data directory C:\Users\Akira\AppData\Roaming\Minerals
Used data directory C:\Users\Akira\AppData\Roaming\Minerals
dbenv.open LogDir=C:\Users\Akira\AppData\Roaming\Minerals\database ErrorFile=C:\Users\Akira\AppData\Roaming\Minerals\db.log
Bound to [::]:33442
Bound to 0.0.0.0:33442
Loading block index...
Opening LevelDB in C:\Users\Akira\AppData\Roaming\Minerals\txleveldb
Opened LevelDB successfully
CBlock(hash=00000c639b0fbf250ba63c6ef2952dbb44bb1051324a27383b8a56fb833d8137, ver=1, hashPrevBlock=0000000000000000000000000000000000000000000000000000000000000000, hashMerkleRoot=18bf53ed0bbbc417c8e2d7993294dba71e1ba10697c9289c617ee02108bb197c, nTime=1402346011, nBits=1e0fffff, nNonce=1912748, vtx=1, vchBlockSig=)
Coinbase(hash=18bf53ed0b, nTime=1402346000, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, 4294967295), coinbase 00012a0530362f3039)
CTxOut(empty)
vMerkleTree: 18bf53ed0b
block.GetHash() == 00000c639b0fbf250ba63c6ef2952dbb44bb1051324a27383b8a56fb833d8137
block.hashMerkleRoot == 18bf53ed0bbbc417c8e2d7993294dba71e1ba10697c9289c617ee02108bb197c
block.nTime = 1402346011
block.nNonce = 1912748
CBlock(hash=00000c639b0fbf250ba63c6ef2952dbb44bb1051324a27383b8a56fb833d8137, ver=1, hashPrevBlock=0000000000000000000000000000000000000000000000000000000000000000, hashMerkleRoot=18bf53ed0bbbc417c8e2d7993294dba71e1ba10697c9289c617ee02108bb197c, nTime=1402346011, nBits=1e0fffff, nNonce=1912748, vtx=1, vchBlockSig=)
Coinbase(hash=18bf53ed0b, nTime=1402346000, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, 4294967295), coinbase 00012a0530362f3039)
CTxOut(empty)
vMerkleTree: 18bf53ed0b
SetBestChain: new best=00000c639b0fbf250ba6 height=0 trust=1048577 blocktrust=1048577 date=06/09/14 20:33:31
ResetSyncCheckpoint: sync-checkpoint reset to 00000c639b0fbf250ba63c6ef2952dbb44bb1051324a27383b8a56fb833d8137
block index 407ms
Loading wallet...
nFileVersion = 1000000
Keys: 0 plaintext, 0 encrypted, 0 w/ metadata, 0 total
Performing wallet upgrade to 60000
keypool added key 1, size=1
keypool added key 2, size=2
keypool added key 3, size=3
keypool added key 4, size=4
keypool added key 5, size=5
keypool added key 6, size=6
keypool added key 7, size=7
keypool added key 8, size=8
keypool added key 9, size=9
keypool added key 10, size=10
keypool added key 11, size=11
keypool added key 12, size=12
keypool added key 13, size=13
keypool added key 14, size=14
keypool added key 15, size=15
keypool added key 16, size=16
keypool added key 17, size=17
keypool added key 18, size=18
keypool added key 19, size=19
keypool added key 20, size=20
keypool added key 21, size=21
keypool added key 22, size=22
keypool added key 23, size=23
keypool added key 24, size=24
keypool added key 25, size=25
keypool added key 26, size=26
keypool added key 27, size=27
keypool added key 28, size=28
keypool added key 29, size=29
keypool added key 30, size=30
keypool added key 31, size=31
keypool added key 32, size=32
keypool added key 33, size=33
keypool added key 34, size=34
keypool added key 35, size=35
keypool added key 36, size=36
keypool added key 37, size=37
keypool added key 38, size=38
keypool added key 39, size=39
keypool added key 40, size=40
keypool added key 41, size=41
keypool added key 42, size=42
keypool added key 43, size=43
keypool added key 44, size=44
keypool added key 45, size=45
keypool added key 46, size=46
keypool added key 47, size=47
keypool added key 48, size=48
keypool added key 49, size=49
keypool added key 50, size=50
keypool added key 51, size=51
keypool added key 52, size=52
keypool added key 53, size=53
keypool added key 54, size=54
keypool added key 55, size=55
keypool added key 56, size=56
keypool added key 57, size=57
keypool added key 58, size=58
keypool added key 59, size=59
keypool added key 60, size=60
keypool added key 61, size=61
keypool added key 62, size=62
keypool added key 63, size=63
keypool added key 64, size=64
keypool added key 65, size=65
keypool added key 66, size=66
keypool added key 67, size=67
keypool added key 68, size=68
keypool added key 69, size=69
keypool added key 70, size=70
keypool added key 71, size=71
keypool added key 72, size=72
keypool added key 73, size=73
keypool added key 74, size=74
keypool added key 75, size=75
keypool added key 76, size=76
keypool added key 77, size=77
keypool added key 78, size=78
keypool added key 79, size=79
keypool added key 80, size=80
keypool added key 81, size=81
keypool added key 82, size=82
keypool added key 83, size=83
keypool added key 84, size=84
keypool added key 85, size=85
keypool added key 86, size=86
keypool added key 87, size=87
keypool added key 88, size=88
keypool added key 89, size=89
keypool added key 90, size=90
keypool added key 91, size=91
keypool added key 92, size=92
keypool added key 93, size=93
keypool added key 94, size=94
keypool added key 95, size=95
keypool added key 96, size=96
keypool added key 97, size=97
keypool added key 98, size=98
keypool added key 99, size=99
keypool added key 100, size=100
keypool added key 101, size=101
keypool keep 1
wallet 31600ms
Loading addresses...
ERROR: CAddrman::Read() : open failed
Invalid or missing peers.dat; recreating
Loaded 0 addresses from peers.dat 1ms
mapBlockIndex.size() = 1
nBestHeight = 0
setKeyPool.size() = 100
mapWallet.size() = 0
mapAddressBook.size() = 1
Done loading
ThreadRPCServer started
ThreadDNSAddressSeed started
Loading addresses from DNS seeds (could take a while)
ThreadIRCSeed exited
ThreadOpenAddedConnections started
ThreadOpenAddedConnections exited
ThreadSocketHandler started
ThreadOpenConnections started
ThreadMessageHandler started
ThreadStakeMiner started
Added 1 addresses from 54.171.92.64: 0 tried, 1 new
Added 1 addresses from 50.63.202.67: 0 tried, 2 new
2 addresses found from DNS seeds
ThreadDNSAddressSeed exited
Flushed 2 addresses to peers.dat 98ms
trying connection 54.171.92.64:33442 lastseen=118.7hrs
GetMyExternalIP() received [81.241.178.59] 81.241.178.59:0
GetMyExternalIP() returned 81.241.178.59
AddLocal(81.241.178.59:33442,5)
connected 54.171.92.64:33442
send version message: version 60013, blocks=0, us=81.241.178.59:33442, them=54.171.92.64:33442, peer=54.171.92.64:33442
sending: version (100 bytes)
trying connection 50.63.202.67:33442 lastseen=105.2hrs
connected 50.63.202.67:33442
send version message: version 60013, blocks=0, us=81.241.178.59:33442, them=50.63.202.67:33442, peer=50.63.202.67:33442
sending: version (100 bytes)
Flushing wallet.dat
Flushed wallet.dat 431ms
Using OpenSSL version OpenSSL 1.0.1j 15 Oct 2014
Startup time: 11/09/14 13:59:55
Default data directory C:\Users\Akira\AppData\Roaming\Minerals
Used data directory C:\Users\Akira\AppData\Roaming\Minerals
dbenv.open LogDir=C:\Users\Akira\AppData\Roaming\Minerals\database ErrorFile=C:\Users\Akira\AppData\Roaming\Minerals\db.log
Bound to [::]:33442
Bound to 0.0.0.0:33442
Loading block index...
Opening LevelDB in C:\Users\Akira\AppData\Roaming\Minerals\txleveldb
Opened LevelDB successfully
CBlock(hash=00000c639b0fbf250ba63c6ef2952dbb44bb1051324a27383b8a56fb833d8137, ver=1, hashPrevBlock=0000000000000000000000000000000000000000000000000000000000000000, hashMerkleRoot=18bf53ed0bbbc417c8e2d7993294dba71e1ba10697c9289c617ee02108bb197c, nTime=1402346011, nBits=1e0fffff, nNonce=1912748, vtx=1, vchBlockSig=)
Coinbase(hash=18bf53ed0b, nTime=1402346000, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, 4294967295), coinbase 00012a0530362f3039)
CTxOut(empty)
vMerkleTree: 18bf53ed0b
block.GetHash() == 00000c639b0fbf250ba63c6ef2952dbb44bb1051324a27383b8a56fb833d8137
block.hashMerkleRoot == 18bf53ed0bbbc417c8e2d7993294dba71e1ba10697c9289c617ee02108bb197c
block.nTime = 1402346011
block.nNonce = 1912748
CBlock(hash=00000c639b0fbf250ba63c6ef2952dbb44bb1051324a27383b8a56fb833d8137, ver=1, hashPrevBlock=0000000000000000000000000000000000000000000000000000000000000000, hashMerkleRoot=18bf53ed0bbbc417c8e2d7993294dba71e1ba10697c9289c617ee02108bb197c, nTime=1402346011, nBits=1e0fffff, nNonce=1912748, vtx=1, vchBlockSig=)
Coinbase(hash=18bf53ed0b, nTime=1402346000, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, 4294967295), coinbase 00012a0530362f3039)
CTxOut(empty)
vMerkleTree: 18bf53ed0b
SetBestChain: new best=00000c639b0fbf250ba6 height=0 trust=1048577 blocktrust=1048577 date=06/09/14 20:33:31
ResetSyncCheckpoint: sync-checkpoint reset to 00000c639b0fbf250ba63c6ef2952dbb44bb1051324a27383b8a56fb833d8137
block index 407ms
Loading wallet...
nFileVersion = 1000000
Keys: 0 plaintext, 0 encrypted, 0 w/ metadata, 0 total
Performing wallet upgrade to 60000
keypool added key 1, size=1
keypool added key 2, size=2
keypool added key 3, size=3
keypool added key 4, size=4
keypool added key 5, size=5
keypool added key 6, size=6
keypool added key 7, size=7
keypool added key 8, size=8
keypool added key 9, size=9
keypool added key 10, size=10
keypool added key 11, size=11
keypool added key 12, size=12
keypool added key 13, size=13
keypool added key 14, size=14
keypool added key 15, size=15
keypool added key 16, size=16
keypool added key 17, size=17
keypool added key 18, size=18
keypool added key 19, size=19
keypool added key 20, size=20
keypool added key 21, size=21
keypool added key 22, size=22
keypool added key 23, size=23
keypool added key 24, size=24
keypool added key 25, size=25
keypool added key 26, size=26
keypool added key 27, size=27
keypool added key 28, size=28
keypool added key 29, size=29
keypool added key 30, size=30
keypool added key 31, size=31
keypool added key 32, size=32
keypool added key 33, size=33
keypool added key 34, size=34
keypool added key 35, size=35
keypool added key 36, size=36
keypool added key 37, size=37
keypool added key 38, size=38
keypool added key 39, size=39
keypool added key 40, size=40
keypool added key 41, size=41
keypool added key 42, size=42
keypool added key 43, size=43
keypool added key 44, size=44
keypool added key 45, size=45
keypool added key 46, size=46
keypool added key 47, size=47
keypool added key 48, size=48
keypool added key 49, size=49
keypool added key 50, size=50
keypool added key 51, size=51
keypool added key 52, size=52
keypool added key 53, size=53
keypool added key 54, size=54
keypool added key 55, size=55
keypool added key 56, size=56
keypool added key 57, size=57
keypool added key 58, size=58
keypool added key 59, size=59
keypool added key 60, size=60
keypool added key 61, size=61
keypool added key 62, size=62
keypool added key 63, size=63
keypool added key 64, size=64
keypool added key 65, size=65
keypool added key 66, size=66
keypool added key 67, size=67
keypool added key 68, size=68
keypool added key 69, size=69
keypool added key 70, size=70
keypool added key 71, size=71
keypool added key 72, size=72
keypool added key 73, size=73
keypool added key 74, size=74
keypool added key 75, size=75
keypool added key 76, size=76
keypool added key 77, size=77
keypool added key 78, size=78
keypool added key 79, size=79
keypool added key 80, size=80
keypool added key 81, size=81
keypool added key 82, size=82
keypool added key 83, size=83
keypool added key 84, size=84
keypool added key 85, size=85
keypool added key 86, size=86
keypool added key 87, size=87
keypool added key 88, size=88
keypool added key 89, size=89
keypool added key 90, size=90
keypool added key 91, size=91
keypool added key 92, size=92
keypool added key 93, size=93
keypool added key 94, size=94
keypool added key 95, size=95
keypool added key 96, size=96
keypool added key 97, size=97
keypool added key 98, size=98
keypool added key 99, size=99
keypool added key 100, size=100
keypool added key 101, size=101
keypool keep 1
wallet 31600ms
Loading addresses...
ERROR: CAddrman::Read() : open failed
Invalid or missing peers.dat; recreating
Loaded 0 addresses from peers.dat 1ms
mapBlockIndex.size() = 1
nBestHeight = 0
setKeyPool.size() = 100
mapWallet.size() = 0
mapAddressBook.size() = 1
Done loading
ThreadRPCServer started
ThreadDNSAddressSeed started
Loading addresses from DNS seeds (could take a while)
ThreadIRCSeed exited
ThreadOpenAddedConnections started
ThreadOpenAddedConnections exited
ThreadSocketHandler started
ThreadOpenConnections started
ThreadMessageHandler started
ThreadStakeMiner started
Added 1 addresses from 54.171.92.64: 0 tried, 1 new
Added 1 addresses from 50.63.202.67: 0 tried, 2 new
2 addresses found from DNS seeds
ThreadDNSAddressSeed exited
Flushed 2 addresses to peers.dat 98ms
trying connection 54.171.92.64:33442 lastseen=118.7hrs
GetMyExternalIP() received [81.241.178.59] 81.241.178.59:0
GetMyExternalIP() returned 81.241.178.59
AddLocal(81.241.178.59:33442,5)
connected 54.171.92.64:33442
send version message: version 60013, blocks=0, us=81.241.178.59:33442, them=54.171.92.64:33442, peer=54.171.92.64:33442
sending: version (100 bytes)
trying connection 50.63.202.67:33442 lastseen=105.2hrs
connected 50.63.202.67:33442
send version message: version 60013, blocks=0, us=81.241.178.59:33442, them=50.63.202.67:33442, peer=50.63.202.67:33442
sending: version (100 bytes)
Flushing wallet.dat
Flushed wallet.dat 431ms
We need to fix this first, because it will also affect the QT wallet. The fixes and workaround presented in various bitcointalk topics for people facing that crash in other PoS wallets did not help.
THANKS! I WILL WAIT FOR NEW WALLET...
Update: I confirm the problem ymod123 faces. After rebooting my POS-box due to a planned kernel upgrade and restarting the Mineralsd, no connections could be made to the network. Bummer :/
So, until the a new wallet is built, you can start it with:
Minerals-qt.exe -seednode=dnsseed.morningminerals.com
./Minerals-qt -seednode=dnsseed.morningminerals.com
./Mineralsd -seednode=dnsseed.morningminerals.com
After a few minutes:
So how many people are running a wallet 24/7 here?
Please open your ports 33442 for inbound TCP traffic to keep the network alive and help newcomers get nodes to fetch blocks.
Request: Can you please report if this worked for you and how many connections you get after a while? Not within 5 minutes, but sometime longer? It would help me in 'testing' the dnsseed? Thank you
my wallet is not synching at all no connection im using still the v1.0.0.0 
Most of us use that wallet. Isn't there any other program blocking it? At work, it doesn't work either because of the reverse proxy & firewall in place. Check your Windows firewall, remove Minerals completely from the list, reboot and give it another try. It should prompt you to open ports for Minerals. Allow both home and public. I hope that this will help you Update: I confirm the problem ymod123 faces. After rebooting my POS-box due to a planned kernel upgrade and restarting the Mineralsd, no connections could be made to the network. Bummer :/
So, until the a new wallet is built, you can start it with:
Minerals-qt.exe -seednode=dnsseed.morningminerals.com
./Minerals-qt -seednode=dnsseed.morningminerals.com
./Mineralsd -seednode=dnsseed.morningminerals.com
After a few minutes:
Code:
{
"version" : "v1.0.0.0",
"protocolversion" : 60013,
"walletversion" : 60000,
"balance" : 70386.52844011,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 617276,
"timeoffset" : 0,
"moneysupply" : 27015914.32826824,
"connections" : 2,
"proxy" : "",
"ip" : "94.***.***.***",
"difficulty" : {
"proof-of-work" : 74.15099844,
"proof-of-stake" : 0.00157180
},
"testnet" : false,
"keypoololdest" : 1403293378,
"keypoolsize" : 101,
"paytxfee" : 0.00001000,
"mininput" : 0.00000000,
"unlocked_until" : 1425138253,
"errors" : ""
}
"version" : "v1.0.0.0",
"protocolversion" : 60013,
"walletversion" : 60000,
"balance" : 70386.52844011,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 617276,
"timeoffset" : 0,
"moneysupply" : 27015914.32826824,
"connections" : 2,
"proxy" : "",
"ip" : "94.***.***.***",
"difficulty" : {
"proof-of-work" : 74.15099844,
"proof-of-stake" : 0.00157180
},
"testnet" : false,
"keypoololdest" : 1403293378,
"keypoolsize" : 101,
"paytxfee" : 0.00001000,
"mininput" : 0.00000000,
"unlocked_until" : 1425138253,
"errors" : ""
}
So how many people are running a wallet 24/7 here?
Please open your ports 33442 for inbound TCP traffic to keep the network alive and help newcomers get nodes to fetch blocks.
Request: Can you please report if this worked for you and how many connections you get after a while? Not within 5 minutes, but sometime longer? It would help me in 'testing' the dnsseed? Thank you
my wallet is not synching at all no connection im using still the v1.0.0.0
Most of us use that wallet. Isn't there any other program blocking it? At work, it doesn't work either because of the reverse proxy & firewall in place. Check your Windows firewall, remove Minerals completely from the list, reboot and give it another try. It should prompt you to open ports for Minerals. Allow both home and public. I hope that this will help you Update: I confirm the problem ymod123 faces. After rebooting my POS-box due to a planned kernel upgrade and restarting the Mineralsd, no connections could be made to the network. Bummer :/
So, until the a new wallet is built, you can start it with:
Minerals-qt.exe -seednode=dnsseed.morningminerals.com
./Minerals-qt -seednode=dnsseed.morningminerals.com
./Mineralsd -seednode=dnsseed.morningminerals.com
After a few minutes:
Code:
{
"version" : "v1.0.0.0",
"protocolversion" : 60013,
"walletversion" : 60000,
"balance" : 70386.52844011,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 617276,
"timeoffset" : 0,
"moneysupply" : 27015914.32826824,
"connections" : 2,
"proxy" : "",
"ip" : "94.***.***.***",
"difficulty" : {
"proof-of-work" : 74.15099844,
"proof-of-stake" : 0.00157180
},
"testnet" : false,
"keypoololdest" : 1403293378,
"keypoolsize" : 101,
"paytxfee" : 0.00001000,
"mininput" : 0.00000000,
"unlocked_until" : 1425138253,
"errors" : ""
}
"version" : "v1.0.0.0",
"protocolversion" : 60013,
"walletversion" : 60000,
"balance" : 70386.52844011,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 617276,
"timeoffset" : 0,
"moneysupply" : 27015914.32826824,
"connections" : 2,
"proxy" : "",
"ip" : "94.***.***.***",
"difficulty" : {
"proof-of-work" : 74.15099844,
"proof-of-stake" : 0.00157180
},
"testnet" : false,
"keypoololdest" : 1403293378,
"keypoolsize" : 101,
"paytxfee" : 0.00001000,
"mininput" : 0.00000000,
"unlocked_until" : 1425138253,
"errors" : ""
}
So how many people are running a wallet 24/7 here?
Please open your ports 33442 for inbound TCP traffic to keep the network alive and help newcomers get nodes to fetch blocks.
Request: Can you please report if this worked for you and how many connections you get after a while? Not within 5 minutes, but sometime longer? It would help me in 'testing' the dnsseed? Thank you
It's syncing for me.... v1 wallet, says 6 connections..
Good news!
Minerals has a DNS seed, meaning the wallet will synchronize automatically right after starting it the first time. It may take a few minutes to get the peers. Currently, five peers are added after a few minutes. If you leave it open for for staking 24/7, you get 39 connections or more.
Yup, it's synchronizing without a Minerals.conf file
I'm going to discuss this and get it tested thoroughly first. Then it needs to be compiled for the different platforms, both 32 and 64 bits. I do not know yet how to do this for Windows and certainly not for Mac. Gitian could be a solutions, or building it natively on the respective platforms.
Also, we need more than one dns seed server. Currently morningminerals is running an instance of the dnsseed server, together with a wallet as supernode. I'm not sure it's a good idea serve block from the VM that also runs the block explorer.
Anyway, I'll keep you posted in further advancements.
Minerals has a DNS seed, meaning the wallet will synchronize automatically right after starting it the first time. It may take a few minutes to get the peers. Currently, five peers are added after a few minutes. If you leave it open for for staking 24/7, you get 39 connections or more.
Yup, it's synchronizing without a Minerals.conf file
I'm going to discuss this and get it tested thoroughly first. Then it needs to be compiled for the different platforms, both 32 and 64 bits. I do not know yet how to do this for Windows and certainly not for Mac. Gitian could be a solutions, or building it natively on the respective platforms.
Also, we need more than one dns seed server. Currently morningminerals is running an instance of the dnsseed server, together with a wallet as supernode. I'm not sure it's a good idea serve block from the VM that also runs the block explorer.
Anyway, I'll keep you posted in further advancements.
my wallet is not synching at all no connection im using still the v1.0.0.0
Good news!
Minerals has a DNS seed, meaning the wallet will synchronize automatically right after starting it the first time. It may take a few minutes to get the peers. Currently, five peers are added after a few minutes. If you leave it open for for staking 24/7, you get 39 connections or more.
Yup, it's synchronizing without a Minerals.conf file
I'm going to discuss this and get it tested thoroughly first. Then it needs to be compiled for the different platforms, both 32 and 64 bits. I do not know yet how to do this for Windows and certainly not for Mac. Gitian could be a solutions, or building it natively on the respective platforms.
Also, we need more than one dns seed server. Currently morningminerals is running an instance of the dnsseed server, together with a wallet as supernode. I'm not sure it's a good idea serve block from the VM that also runs the block explorer.
Anyway, I'll keep you posted in further advancements.
Minerals has a DNS seed, meaning the wallet will synchronize automatically right after starting it the first time. It may take a few minutes to get the peers. Currently, five peers are added after a few minutes. If you leave it open for for staking 24/7, you get 39 connections or more.
Yup, it's synchronizing without a Minerals.conf file
I'm going to discuss this and get it tested thoroughly first. Then it needs to be compiled for the different platforms, both 32 and 64 bits. I do not know yet how to do this for Windows and certainly not for Mac. Gitian could be a solutions, or building it natively on the respective platforms.
Also, we need more than one dns seed server. Currently morningminerals is running an instance of the dnsseed server, together with a wallet as supernode. I'm not sure it's a good idea serve block from the VM that also runs the block explorer.
Anyway, I'll keep you posted in further advancements.
DNS propagation for the seeder seems to be successful (except for India)
On the other hand, the wallet doesn't get its list of nodes. I might have done something wrong, but it's already very late, so I might have forgotten something along the way
The output is not what I expect... Anyway, tomorrow's another day ^^
On the other hand, the wallet doesn't get its list of nodes. I might have done something wrong, but it's already very late, so I might have forgotten something along the way
Code:
$ sudo ./dnsseed -h dnsseed.morningminerals.com -n xxx.xxx.xxx.xxx
Starting 4 DNS threads for dnsseed.morningminerals.com on xxx.xxx.xxx.xxx (port 53).......done
Starting seeder...done
Starting 96 crawler threads...done
[14-11-02 23:17:23] 0/2 available (2 tried in 285s, 0 new, 0 active), 0 banned; 0 DNS requests, 4 db queries
Starting 4 DNS threads for dnsseed.morningminerals.com on xxx.xxx.xxx.xxx (port 53).......done
Starting seeder...done
Starting 96 crawler threads...done
[14-11-02 23:17:23] 0/2 available (2 tried in 285s, 0 new, 0 active), 0 banned; 0 DNS requests, 4 db queries
The output is not what I expect... Anyway, tomorrow's another day ^^
On page 460 I posted 2 different Mega links, with the different wallets. Try either of them.
You can omit listen. It's only used to listen for RPC calls, which you don't really need for normal use.
Work is being done on the wallet to include new dns seeds, so you don't need to mess with the configuration.
You can omit listen. It's only used to listen for RPC calls, which you don't really need for normal use.
Work is being done on the wallet to include new dns seeds, so you don't need to mess with the configuration.
Jump to: