Logo contest has finally ended! The new logo has been chosen and the winner will still be making some changes to the alternative logo, but the primary logo should be finished, website will be up soon:
Topic: [ANN] microCoin MRC - alcurEX - Scrypt-Jane - nFactor - page 160. (Read 374705 times)
Sorry for the late inactivity, but we have been busy with work on our future announcement. Rest assured microCoin is still going. The current policy is that we will be keeping a somewhat low profile for a while and do more promotion for microCoin later after our future announcement. Consider this a good chance to get some easy microCoin.
Logo contest has finally ended! The new logo has been chosen and the winner will still be making some changes to the alternative logo, but the primary logo should be finished, website will be up soon:
Logo contest has finally ended! The new logo has been chosen and the winner will still be making some changes to the alternative logo, but the primary logo should be finished, website will be up soon:
Just note microCoin can write like µ too (alt+230). We have own currency letter 
100MRC = 100µ
100MRC = 100µ
Getting 100% rejected shares today on the minersbest pool.. 100% accepted last night, seems to have gone overnight?
Edit: Actually I'm getting 100% rejects on every pool, not just minersbest.. No configuration changes on the miners. Could the diff change affect this?
Edit: Actually I'm getting 100% rejects on every pool, not just minersbest.. No configuration changes on the miners. Could the diff change affect this?
has there been a dif change?
I think its just some problem on your end to be honest
Getting this too with the latest cudaminer (github) with MRC support. I copied the MicroCoin N-factor parameters right out of src/main.cpp (in the MicroCoin github repo) into cudaminer.
Time to solo-mine, I guess!
Christian
Getting 100% rejected shares today on the minersbest pool.. 100% accepted last night, seems to have gone overnight?
Edit: Actually I'm getting 100% rejects on every pool, not just minersbest.. No configuration changes on the miners. Could the diff change affect this?
Edit: Actually I'm getting 100% rejects on every pool, not just minersbest.. No configuration changes on the miners. Could the diff change affect this?
has there been a dif change?
I think its just some problem on your end to be honest
Getting this too with the latest cudaminer (github) with MRC support. I copied the MicroCoin N-factor parameters right out of src/main.cpp (in the MicroCoin github repo) into cudaminer.
Time to solo-mine, I guess!
Christian
Reply from Cryptsy:
"I have added it to the list of coins to be reviewed for addition to he Cryptsy exchange!"
"I have added it to the list of coins to be reviewed for addition to he Cryptsy exchange!"
Mmmhh
in my opinion that should attract to many dumpers i think..at least if they would put on Crypsty for 90 satoshi at least , could be a good start 
Anyway, those who will dump - regret. I buy as many as possibe lol!
AND I DAMNED LIKE MRC!
Ofcource it's good to get listed on craptsy... just hope couple weeks more easy 300mh/s network mining
Reply from Cryptsy:
"I have added it to the list of coins to be reviewed for addition to he Cryptsy exchange!"
"I have added it to the list of coins to be reviewed for addition to he Cryptsy exchange!"
Mmmhh
in my opinion that should attract to many dumpers i think..at least if they would put on Crypsty for 90 satoshi at least , could be a good start Anyway, those who will dump - regret. I buy as many as possibe lol!
AND I DAMNED LIKE MRC!
Of course mate
...nice blue sign however! 
Reply from Cryptsy:
"I have added it to the list of coins to be reviewed for addition to he Cryptsy exchange!"
"I have added it to the list of coins to be reviewed for addition to he Cryptsy exchange!"
Mmmhh
in my opinion that should attract to many dumpers i think..at least if they would put on Crypsty for 90 satoshi at least , could be a good start Anyway, those who will dump - regret. I buy as many as possibe lol!
AND I DAMNED LIKE MRC!
Reply from Cryptsy:
"I have added it to the list of coins to be reviewed for addition to he Cryptsy exchange!"
"I have added it to the list of coins to be reviewed for addition to he Cryptsy exchange!"
Mmmhh
in my opinion that should attract to many dumpers i think..at least if they would put on Crypsty for 90 satoshi at least , could be a good start
Reply from Cryptsy:
"I have added it to the list of coins to be reviewed for addition to he Cryptsy exchange!"
"I have added it to the list of coins to be reviewed for addition to he Cryptsy exchange!"
Getting 100% rejected shares today on the minersbest pool.. 100% accepted last night, seems to have gone overnight?
Edit: Actually I'm getting 100% rejects on every pool, not just minersbest.. No configuration changes on the miners. Could the diff change affect this?
Edit: Actually I'm getting 100% rejects on every pool, not just minersbest.. No configuration changes on the miners. Could the diff change affect this?
has there been a dif change?
I think its just some problem on your end to be honest
2 different miners (CPU and GPU) both returning rejected shares - "Share above target" - on 2 different pools
Getting 100% rejected shares today on the minersbest pool.. 100% accepted last night, seems to have gone overnight?
Edit: Actually I'm getting 100% rejects on every pool, not just minersbest.. No configuration changes on the miners. Could the diff change affect this?
Edit: Actually I'm getting 100% rejects on every pool, not just minersbest.. No configuration changes on the miners. Could the diff change affect this?
has there been a dif change?
I think its just some problem on your end to be honest
Getting 100% rejected shares today on the minersbest pool.. 100% accepted last night, seems to have gone overnight?
Edit: Actually I'm getting 100% rejects on every pool, not just minersbest.. No configuration changes on the miners. Could the diff change affect this?
Edit: Actually I'm getting 100% rejects on every pool, not just minersbest.. No configuration changes on the miners. Could the diff change affect this?
i don't know why all nodes don't work for me
Quote
If port is problem, we can inform dev so they can solve that on next wallet update.
We hope update wallet.
addnode=84.251.34.142:3232
addnode=145.220.255.56:35937
addnode=24.155.217.218:62494
addnode=183.171.178.11:10278
hmm so I tried again on my friends computer and it seems microcoin is updating now... Strange, as i've tried at least 10 times before during a period of about 2 weeks to get it updating...
I think its because of the new addnodes, cause without them it's still not updating (altho the addnode list without them is also kinda old, since I didnt look at it for a little while)...
Anyway problem resolved for that computer and it is connecting now. Seems port 4444 might be blocked I guess >.<
Please DEV. Can you add this solution on first page.
And maybe if we take new port for nodes.. so China can join in
hmm seems its still not totally resolved tho, decided to test it a little more and remove all nodes except the ones you posted...
client is again not updating now (although it does show 2 active connections to network), might start updating later, but i've already waited for about 5-10 minutes and still not updating the block chain. No idea what it is doing tho
Before I wouldn't get any active connections to the network tho, so it's definitely an improvement, but not sure if/when it starts updating the blockchain...
I'll just let it try to update for about another half an hour, will post here if it does update
ok, just 1 active connection now but it did manage to sync (altho I never saw the updating blockchain bar I think)... Anyway, it's updated, tested it by sending 1 MRC to the wallet and it was received right away... Awesome!
Problem is that the number of connections doesn't really seem to go up, so when the node goes down I guess it will still be troublesome >.<
If I put only 84.251.34.142:3232 I get four connection same way.
... now I have 7...
And I have no uPnp enabled.
Any way 84.251.34.142:3232 is active all the time.
I know because it is same server ip than first node and block chain explorer.
... now 10 connection
After taking a quick look at the log file it seems maybe these nodes are unrelated to the problem being solved...
I just took a quick look tho, dont rly have time to check it in depth right now, maybe tonight...
Anyway the log in case you're interested:
Code:
microCoin version v1.1.1.0-gunit-beta (187)
Using OpenSSL version OpenSSL 1.0.1e 11 Feb 2013
Startup time: 01/27/14 06:42:41
Default data directory C:\Users\Miner2\AppData\Roaming\microCoin
Used data directory C:\Users\Miner2\AppData\Roaming\microCoin
dbenv.open LogDir=C:\Users\Miner2\AppData\Roaming\microCoin\database ErrorFile=C:\Users\Miner2\AppData\Roaming\microCoin\db.log
Bound to [::]:4444
Bound to 0.0.0.0:4444
Loading block index...
LoadBlockIndex(): hashBestChain=000000000b4abc133800 height=57376 trust=57377 date=01/27/14 06:41:53
LoadBlockIndex(): synchronized checkpoint 00000a475a000e653d8edb0535fa29f7a1a9e73ae82547684e6bd8df012e6789
Verifying last 2500 blocks at level 1
block index 12494ms
Loading wallet...
nFileVersion = 70200
wallet 582ms
Loading addresses...
Loaded 1643 addresses from peers.dat 4ms
RandAddSeed() 180828 bytes
mapBlockIndex.size() = 57377
nBestHeight = 57376
setKeyPool.size() = 101
mapWallet.size() = 1
mapAddressBook.size() = 1
send version message: version 70000, blocks=57376, us=0.0.0.0:0, them=0.0.0.0:0, peer=127.0.0.1:0
Done loading
ThreadRPCServer started
AddLocal([2001:0:9d38:6ab8:7c:e9e2:c5e8:a645]:4444,1)
DNS seeding disabled
ThreadMapPort started
ThreadIRCSeed started
ThreadSocketHandler started
ThreadOpenAddedConnections started
trying connection 37.123.187.23:57060 lastseen=358556.9hrs
ThreadOpenConnections started
trying connection 84.251.34.142:44444 lastseen=0.0hrs
ThreadMessageHandler started
ThreadStakeMinter started
CPUMiner started for proof-of-stake
refreshWallet
Flushed 1643 addresses to peers.dat 22ms
ipcThread started
connected 84.251.34.142:44444
send version message: version 70000, blocks=57376, us=[2001:0:9d38:6ab8:7c:e9e2:c5e8:a645]:4444, them=84.251.34.142:44444, peer=84.251.34.142:44444
IRC :irc.smutfairy.com NOTICE AUTH :*** Looking up your hostname...
IRC :irc.smutfairy.com NOTICE AUTH :*** Couldn't look up your hostname
IRC SENDING: NICK x819233593
IRC SENDING: USER x819233593 8 * : x819233593
trying connection 91.229.2.250:4444 lastseen=1.9hrs
keypool return 2
keypool return 2
IRC :irc.smutfairy.com 001 x819233593 :Welcome to the LFNet Internet Relay Chat Network x819233593
IRC :irc.smutfairy.com 002 x819233593 :Your host is irc.smutfairy.com[192.75.207.148/6667], running version hybrid-7.2.3
IRC :irc.smutfairy.com 003 x819233593 :This server was created May 26 2011 at 23:04:42
IRC :irc.smutfairy.com 004 x819233593 irc.smutfairy.com hybrid-7.2.3 CDGabcdfgiklnorsuwxyz biklmnopstveI bkloveI
UPnP: ExternalIPAddress = 101.245.159.4
AddLocal(101.245.159.4:4444,3)
UPnP Port Mapping successful.
keypool return 2
IRC SENDING: USERHOST x819233593
keypool return 2
IRC :irc.smutfairy.com 302 x819233593 :[email protected]
GetIPFromIRC() got userhost 218.11.179.135
GetIPFromIRC() returned 218.11.179.135
AddLocal(218.11.179.135:4444,4)
IRC SENDING: NICK uDFWgmQP1yrQKmv
IRC SENDING: JOIN #microCoin224
IRC SENDING: WHO #microCoin224
keypool return 2
IRC got join
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
keypool return 2
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
keypool return 2
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
keypool return 2
connection timeout
ERROR: GetMyExternalIP() : connection to 91.198.22.70:80 failed
connection timeout
keypool return 2
trying connection 89.133.17.144:27694 lastseen=358556.9hrs
keypool return 2
connection timeout
keypool return 2
trying connection 67.252.105.243:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
ERROR: GetMyExternalIP() : connection to 74.208.43.192:80 failed
keypool return 2
recv failed: 10054
ERROR: GetMyExternalIP() : connection closed
connection timeout
keypool return 2
trying connection 89.137.177.116:4444 lastseen=358556.9hrs
keypool return 2
connection timeout
keypool return 2
trying connection 81.142.137.153:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
ERROR: GetMyExternalIP() : connection to 212.117.175.194:80 failed
keypool return 2
connection timeout
keypool return 2
trying connection 71.84.113.165:64929 lastseen=358556.9hrs
keypool return 2
connection timeout
keypool return 2
trying connection 116.224.95.60:4444 lastseen=0.1hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 109.193.194.75:4507 lastseen=358556.9hrs
keypool return 2
connection timeout
keypool return 2
trying connection 91.189.241.192:4444 lastseen=4.2hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 116.231.116.211:55456 lastseen=358556.9hrs
keypool return 2
connection timeout
keypool return 2
keypool return 2
trying connection 174.100.38.43:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 192.186.13.16:49555 lastseen=358556.9hrs
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 101.160.22.189:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 213.230.77.250:43638 lastseen=358556.9hrs
keypool return 2
connection timeout
keypool return 2
trying connection 183.171.178.136:4444 lastseen=1.3hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 144.76.202.45:53495 lastseen=358556.9hrs
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 46.249.59.220:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 31.31.51.7:49401 lastseen=358557.0hrs
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 31.202.203.41:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 77.249.186.174:50661 lastseen=358557.0hrs
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 117.184.44.72:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 173.252.11.32:50744 lastseen=358557.0hrs
keypool return 2
socket no message in first 60 seconds, 0 1
disconnecting node 84.251.34.142:44444
connection timeout
trying connection 145.220.255.43:4444 lastseen=0.9hrs
connection timeout
trying connection 79.219.176.107:63602 lastseen=358557.0hrs
connection timeout
trying connection 116.224.95.60:4444 lastseen=0.1hrs
connection timeout
trying connection 114.85.209.107:62922 lastseen=358557.0hrs
connection timeout
trying connection 116.224.95.60:4444 lastseen=0.1hrs
connection timeout
trying connection 50.100.142.88:9564 lastseen=358557.0hrs
connection timeout
trying connection 46.159.226.22:4444 lastseen=29.5hrs
connection timeout
trying connection 145.220.255.61:41454 lastseen=358557.0hrs
connection timeout
trying connection 116.224.95.60:4444 lastseen=0.1hrs
connection timeout
trying connection 145.220.255.44:48965 lastseen=358557.0hrs
IRC got join
connection timeout
trying connection 120.28.125.96:4444 lastseen=1.5hrs
connection timeout
trying connection 84.251.34.142:55324 lastseen=358557.0hrs
connection timeout
trying connection 145.220.255.50:4444 lastseen=0.9hrs
connection timeout
trying connection 162.243.223.190:52298 lastseen=358557.0hrs
connection timeout
Flushed 1643 addresses to peers.dat 15ms
trying connection 99.7.118.19:4444 lastseen=0.9hrs
connection timeout
trying connection 37.59.25.43:44139 lastseen=358557.0hrs
connection timeout
trying connection 116.224.95.60:4444 lastseen=0.1hrs
connection timeout
trying connection 174.95.58.174:56353 lastseen=358557.0hrs
connection timeout
trying connection 116.224.95.60:4444 lastseen=0.1hrs
connection timeout
trying connection 178.159.23.251:52201 lastseen=358557.0hrs
connection timeout
trying connection 145.220.255.43:4444 lastseen=0.9hrs
connection timeout
trying connection 91.158.104.106:52448 lastseen=358557.0hrs
connection timeout
trying connection 174.100.38.43:4444 lastseen=0.9hrs
connection timeout
trying connection 77.73.139.31:61277 lastseen=358557.0hrs
connection timeout
trying connection 72.66.102.124:4444 lastseen=0.9hrs
connection timeout
trying connection 62.163.9.155:65171 lastseen=358557.0hrs
connection timeout
trying connection 193.93.26.43:4444 lastseen=2.0hrs
connection timeout
trying connection 159.224.220.21:49727 lastseen=358557.0hrs
connection timeout
trying connection 83.252.69.246:4444 lastseen=2.0hrs
connection timeout
trying connection 178.184.176.184:49391 lastseen=358557.0hrs
connection timeout
trying connection 91.189.241.192:4444 lastseen=4.3hrs
IRC got join
connection timeout
trying connection 84.251.34.142:3232 lastseen=358557.0hrs
connection timeout
trying connection 85.65.73.221:4444 lastseen=0.9hrs
connection timeout
trying connection 145.220.255.56:35937 lastseen=358557.0hrs
connection timeout
trying connection 116.224.95.60:4444 lastseen=0.1hrs
connection timeout
trying connection 24.155.217.218:62494 lastseen=358557.0hrs
connection timeout
trying connection 67.255.7.120:4444 lastseen=0.9hrs
connection timeout
trying connection 183.171.178.11:10278 lastseen=358557.0hrs
connection timeout
trying connection 194.34.12.253:4444 lastseen=1.2hrs
connection timeout
trying connection 89.254.243.232:51701 lastseen=358557.0hrs
connection timeout
trying connection 193.158.162.212:4444 lastseen=2.0hrs
connection timeout
connection timeout
trying connection 116.224.95.60:4444 lastseen=0.2hrs
connection timeout
trying connection 54.203.141.180:4444 lastseen=0.9hrs
connection timeout
trying connection 89.20.233.242:4444 lastseen=0.9hrs
connection timeout
trying connection 99.7.118.19:4444 lastseen=0.9hrs
connection timeout
trying connection 192.3.150.86:4444 lastseen=0.9hrs
Flushed 1643 addresses to peers.dat 15ms
connection timeout
trying connection 116.224.95.60:4444 lastseen=0.2hrs
connection timeout
trying connection 117.184.44.72:4444 lastseen=0.9hrs
connection timeout
trying connection 145.220.255.42:4444 lastseen=0.9hrs
connection timeout
trying connection 116.224.95.60:4444 lastseen=0.2hrs
connected 116.224.95.60:4444
send version message: version 70000, blocks=57376, us=218.11.179.135:4444, them=116.224.95.60:4444, peer=116.224.95.60:4444
Added time data, samples 2, offset +4 (+0 minutes)
receive version message: version 70000, blocks=57386, us=60.55.9.51:1759, them=116.224.95.60:4444, peer=116.224.95.60:4444
received block 000000002484b546a405
SetBestChain: new best=000000002484b546a405 height=57377 trust=57378 date=01/27/14 06:41:57
ProcessBlock: ACCEPTED
received block 0000000029a03fc712a8
SetBestChain: new best=0000000029a03fc712a8 height=57378 trust=57379 date=01/27/14 06:42:47
ProcessBlock: ACCEPTED
keypool return 2
received block 000000003462315d20a2
SetBestChain: new best=000000003462315d20a2 height=57379 trust=57380 date=01/27/14 06:43:50
ProcessBlock: ACCEPTED
received block 0000000032fd076127c5
SetBestChain: new best=0000000032fd076127c5 height=57380 trust=57381 date=01/27/14 06:43:53
ProcessBlock: ACCEPTED
received block 00000000427f315f6247
SetBestChain: new best=00000000427f315f6247 height=57381 trust=57382 date=01/27/14 06:44:36
ProcessBlock: ACCEPTED
received block 000000002acae7cf8b1c
SetBestChain: new best=000000002acae7cf8b1c height=57382 trust=57383 date=01/27/14 06:45:30
ProcessBlock: ACCEPTED
received block 000000000deb96f20b5c
SetBestChain: new best=000000000deb96f20b5c height=57383 trust=57384 date=01/27/14 06:45:04
ProcessBlock: ACCEPTED
received block 000000000275d25463de
SetBestChain: new best=000000000275d25463de height=57384 trust=57385 date=01/27/14 06:46:20
ProcessBlock: ACCEPTED
received block 0000000004dd1012cffe
trying connection 112.65.211.237:4444 lastseen=2.0hrs
SetBestChain: new best=0000000004dd1012cffe height=57385 trust=57386 date=01/27/14 06:46:23
ProcessBlock: ACCEPTED
keypool return 2
received block 0000000008abc48163c0
SetBestChain: new best=0000000008abc48163c0 height=57386 trust=57387 date=01/27/14 06:46:25
ProcessBlock: ACCEPTED
Added 171 addresses from 116.224.95.60: 1 tried, 1767 new
keypool return 2
keypool return 2
keypool return 2
keypool return 2
Flushing wallet.dat
Flushed wallet.dat 29ms
keypool return 2
keypool return 2
keypool return 2
CTxMemPool::accept() : accepted cb7175f09c (poolsz 1)
CTxMemPool::accept() : accepted 2c5ea76dcb (poolsz 2)
CTxMemPool::accept() : accepted 0daca947c4 (poolsz 3)
keypool return 2
CTxMemPool::accept() : accepted 3600a79cd9 (poolsz 4)
keypool return 2
connection timeout
keypool return 2
trying connection 178.84.245.4:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 76.188.218.170:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 72.66.102.124:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 89.21.79.8:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 72.66.102.124:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 117.184.44.72:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 72.66.102.124:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
trying connection 145.220.255.59:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
connection timeout
keypool return 2
keypool return 2
trying connection 67.255.7.120:4444 lastseen=0.9hrs
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
keypool return 2
CommitTransaction:
CTransaction(hash=e14f146949, nTime=1390805251, ver=1, vin.size=1, vout.size=2, nLockTime=0)
CTxIn(COutPoint(3b7edf0867, 1), scriptSig=304402204dbdcfea9c6a3472)
CTxOut(nValue=0.0000089, scriptPubKey=OP_DUP OP_HASH160 978309702f3b3a8caf41daa18667ac19f6aa17be OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=0.000001, scriptPubKey=OP_DUP OP_HASH160 9c3fd13f0e77a44cca8d0108e1222508de90d77d OP_EQUALVERIFY OP_CHECKSIG)
connection timeout
keypool keep 2
AddToWallet e14f146949 new
WalletUpdateSpent found spent coin 0.00001yac 3b7edf08676dc018fcee35f5947172b67f5c291f9b2902b57fc75952f48e6716
NotifyTransactionChanged 3b7edf08676dc018fcee35f5947172b67f5c291f9b2902b57fc75952f48e6716 status=1
NotifyTransactionChanged e14f14694921f232880ad8d9fa95d6b29510cab0209ef1e2d3e70333d5771781 status=0
NotifyTransactionChanged 3b7edf08676dc018fcee35f5947172b67f5c291f9b2902b57fc75952f48e6716 status=1
CTxMemPool::accept() : accepted e14f146949 (poolsz 5)
Relaying wtx e14f146949
keypool added key 103, size=101
NotifyAddressBookChanged 1FFAs2yWFcvLsn9evtygPuTjJP71Hqs6vo Bas isMine=0 status=0
updateWallet 3b7edf08676dc018fcee35f5947172b67f5c291f9b2902b57fc75952f48e6716 1
inWallet=1 inModel=1 Index=0-1 showTransaction=1 derivedStatus=1
updateWallet e14f14694921f232880ad8d9fa95d6b29510cab0209ef1e2d3e70333d5771781 0
inWallet=1 inModel=0 Index=1-1 showTransaction=1 derivedStatus=0
keypool return 3
updateWallet 3b7edf08676dc018fcee35f5947172b67f5c291f9b2902b57fc75952f48e6716 1
inWallet=1 inModel=1 Index=0-1 showTransaction=1 derivedStatus=1
received getdata for: tx e14f14694921f232880a
trying connection 101.160.22.189:4444 lastseen=0.9hrs
keypool return 3
keypool return 3
keypool return 3
Flushing wallet.dat
Flushed wallet.dat 32ms
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
received block 000000002f947f1aa2fb
connection timeout
SetBestChain: new best=000000002f947f1aa2fb height=57387 trust=57388 date=01/27/14 06:47:30
ProcessBlock: ACCEPTED
keypool return 3
trying connection 89.20.233.242:4444 lastseen=0.9hrs
keypool return 3
keypool return 3
Flushing wallet.dat
Flushed wallet.dat 30ms
keypool return 3
keypool return 3
keypool return 3
keypool return 3
CTxMemPool::accept() : accepted adb37dd913 (poolsz 2)
CTxMemPool::accept() : accepted 61f0ade4c9 (poolsz 3)
keypool return 3
keypool return 3
keypool return 3
keypool return 3
connection timeout
keypool return 3
trying connection 72.23.64.121:4444 lastseen=0.9hrs
keypool return 3
CTxMemPool::accept() : accepted 2f50280b54 (poolsz 4)
CTxMemPool::accept() : accepted 7347ddfb93 (poolsz 5)
CTxMemPool::accept() : accepted 6eea2de1e8 (poolsz 6)
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
connection timeout
keypool return 3
trying connection 31.202.203.41:4444 lastseen=1.0hrs
keypool return 3
trying connection 37.123.187.23:57060 lastseen=358557.0hrs
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
connection timeout
Flushed 1768 addresses to peers.dat 17ms
keypool return 3
trying connection 82.202.108.19:4444 lastseen=0.9hrs
keypool return 3
connection timeout
keypool return 3
trying connection 89.133.17.144:27694 lastseen=358557.0hrs
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
connection timeout
keypool return 3
trying connection 67.252.105.243:4444 lastseen=0.9hrs
keypool return 3
connection timeout
keypool return 3
trying connection 89.137.177.116:4444 lastseen=358557.0hrs
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
connection timeout
keypool return 3
trying connection 93.233.117.89:4444 lastseen=0.9hrs
keypool return 3
connection timeout
keypool return 3
trying connection 71.84.113.165:64929 lastseen=358557.0hrs
keypool return 3
IRC got join
keypool return 3
keypool return 3
keypool return 3
keypool return 3
keypool return 3
I wish the coin would get added to coinmarket.io (altho its down now)..
It's a great new exchange that's fast and generally works well...
The current exchanges seem to be more in a beta phase and people don't really want to deposit their stuff there (if they would have the opportunity)...
Anyway over time it'll all get fixed
+1 It's a great new exchange that's fast and generally works well...
The current exchanges seem to be more in a beta phase and people don't really want to deposit their stuff there (if they would have the opportunity)...
Anyway over time it'll all get fixed
Quote
If port is problem, we can inform dev so they can solve that on next wallet update.
We hope update wallet.
addnode=84.251.34.142:3232
addnode=145.220.255.56:35937
addnode=24.155.217.218:62494
addnode=183.171.178.11:10278
hmm so I tried again on my friends computer and it seems microcoin is updating now... Strange, as i've tried at least 10 times before during a period of about 2 weeks to get it updating...
I think its because of the new addnodes, cause without them it's still not updating (altho the addnode list without them is also kinda old, since I didnt look at it for a little while)...
Anyway problem resolved for that computer and it is connecting now. Seems port 4444 might be blocked I guess >.<
Please DEV. Can you add this solution on first page.
And maybe if we take new port for nodes.. so China can join in
hmm seems its still not totally resolved tho, decided to test it a little more and remove all nodes except the ones you posted...
client is again not updating now (although it does show 2 active connections to network), might start updating later, but i've already waited for about 5-10 minutes and still not updating the block chain. No idea what it is doing tho
Before I wouldn't get any active connections to the network tho, so it's definitely an improvement, but not sure if/when it starts updating the blockchain...
I'll just let it try to update for about another half an hour, will post here if it does update
ok, just 1 active connection now but it did manage to sync (altho I never saw the updating blockchain bar I think)... Anyway, it's updated, tested it by sending 1 MRC to the wallet and it was received right away... Awesome!
Problem is that the number of connections doesn't really seem to go up, so when the node goes down I guess it will still be troublesome >.<
If I put only 84.251.34.142:3232 I get four connection same way.
... now I have 7...
And I have no uPnp enabled.
Any way 84.251.34.142:3232 is active all the time.
I know because it is same server ip than first node and block chain explorer.
... now 10 connection
I wish the coin would get added to coinmarket.io (altho its down now)..
It's a great new exchange that's fast and generally works well...
The current exchanges seem to be more in a beta phase and people don't really want to deposit their stuff there (if they would have the opportunity)...
Anyway over time it'll all get fixed
It's a great new exchange that's fast and generally works well...
The current exchanges seem to be more in a beta phase and people don't really want to deposit their stuff there (if they would have the opportunity)...
Anyway over time it'll all get fixed
Quote
If port is problem, we can inform dev so they can solve that on next wallet update.
We hope update wallet.
addnode=84.251.34.142:3232
addnode=145.220.255.56:35937
addnode=24.155.217.218:62494
addnode=183.171.178.11:10278
hmm so I tried again on my friends computer and it seems microcoin is updating now... Strange, as i've tried at least 10 times before during a period of about 2 weeks to get it updating...
I think its because of the new addnodes, cause without them it's still not updating (altho the addnode list without them is also kinda old, since I didnt look at it for a little while)...
Anyway problem resolved for that computer and it is connecting now. Seems port 4444 might be blocked I guess >.<
Please DEV. Can you add this solution on first page.
And maybe if we take new port for nodes.. so China can join in
hmm seems its still not totally resolved tho, decided to test it a little more and remove all nodes except the ones you posted...
client is again not updating now (although it does show 2 active connections to network), might start updating later, but i've already waited for about 5-10 minutes and still not updating the block chain. No idea what it is doing tho
Before I wouldn't get any active connections to the network tho, so it's definitely an improvement, but not sure if/when it starts updating the blockchain...
I'll just let it try to update for about another half an hour, will post here if it does update
ok, just 1 active connection now but it did manage to sync (altho I never saw the updating blockchain bar I think)... Anyway, it's updated, tested it by sending 1 MRC to the wallet and it was received right away... Awesome!
Problem is that the number of connections doesn't really seem to go up, so when the node goes down I guess it will still be troublesome >.<
Quote
If port is problem, we can inform dev so they can solve that on next wallet update.
We hope update wallet.
addnode=84.251.34.142:3232
addnode=145.220.255.56:35937
addnode=24.155.217.218:62494
addnode=183.171.178.11:10278
hmm so I tried again on my friends computer and it seems microcoin is updating now... Strange, as i've tried at least 10 times before during a period of about 2 weeks to get it updating...
I think its because of the new addnodes, cause without them it's still not updating (altho the addnode list without them is also kinda old, since I didnt look at it for a little while)...
Anyway problem resolved for that computer and it is connecting now. Seems port 4444 might be blocked I guess >.<
Please DEV. Can you add this solution on first page.
And maybe if we take new port for nodes.. so China can join in
hmm seems its still not totally resolved tho, decided to test it a little more and remove all nodes except the ones you posted...
client is again not updating now (although it does show 2 active connections to network), might start updating later, but i've already waited for about 5-10 minutes and still not updating the block chain. No idea what it is doing tho
Before I wouldn't get any active connections to the network tho, so it's definitely an improvement, but not sure if/when it starts updating the blockchain...
I'll just let it try to update for about another half an hour, will post here if it does update
Quote
If port is problem, we can inform dev so they can solve that on next wallet update.
We hope update wallet.
addnode=84.251.34.142:3232
addnode=145.220.255.56:35937
addnode=24.155.217.218:62494
addnode=183.171.178.11:10278
hmm so I tried again on my friends computer and it seems microcoin is updating now... Strange, as i've tried at least 10 times before during a period of about 2 weeks to get it updating...
I think its because of the new addnodes, cause without them it's still not updating (altho the addnode list without them is also kinda old, since I didnt look at it for a little while)...
Anyway problem resolved for that computer and it is connecting now. Seems port 4444 might be blocked I guess >.<
Please DEV. Can you add this solution on first page.
And maybe if we take new port for nodes.. so China can join in
hmm seems its still not totally resolved tho, decided to test it a little more and remove all nodes except the ones you posted...
client is again not updating now (although it does show 2 active connections to network), might start updating later, but i've already waited for about 5-10 minutes and still not updating the block chain. No idea what it is doing tho
Before I wouldn't get any active connections to the network tho, so it's definitely an improvement, but not sure if/when it starts updating the blockchain...
I'll just let it try to update for about another half an hour, will post here if it does update
Jump to: