|
cygnus.conf. Inside i have this: (deleting and redoing the conf file i tried, didint help)
addnode=46.236.161.66
addnode=136.243.50.159
addnode=199.7.156.130
addnode=70.83.227.32
addnode= 5.67.142.54
addnode=216.189.153.244
addnode=78.94.32.195
addnode=77.110.148.98
addnode=104.47.141.18
addnode=213.168.249.109
addnode=77.200.5.30
|
|
|
|
|
Guys, a bit of help if you dont mind. Can sync the wallet, added all nodes to cygnus.conf, but nothing is going on.... tried to re install, still nothing
|
|
|
|
|
As good as decred or better? In any case looks like a very interesting project
|
|
|
|
|
Вывел через Александра 30+т.р. (не первый раз) вся процедура заняла не более 3 - 4 минут.
Все оперативно как всегда.
Намного удобнее и быстрее чем через других и/или другие сервисы, а ля web или yandex money (к тому же дешевле)
|
|
|
|
|
ok can anyone help? maybe i need to update nodes? i tried adding the nodes here, but still 1 connection
|
|
|
|
Small update here, thanks for waiting. We will have the mac wallet released shortly, we just have to test it before publishing it to Github. There is a lot of work going on behind the scenes on the arbitration bot, so we will hopefully have something to show here within a week.
Why is there only 1 connection and why are staked coins never accepted? |
|
|
|
|
can someone give me updated node list (only have 1 connection)
ok - balance shows, but still 1 connection
|
|
|
|
|
ok.... thats not good! its been 30 + minutes. is there an irs channel? (wallet is synched)
|
|
|
|
|
Send coins from bittrex to wallet, exchange says transaction completed and block explorer shows right balance for adress, but i dont see the coins in my wallet. Why is that, and how long can this take? Is this normal?
|
|
|
|
|
To the moon? When is a website going to be up?
|
|
|
|
|
how funny is it when people who bought hugh are shouting at the dev.... is it the devs fault the market went that way? Ofcourse not - its you people who specualte on the market, in hope of making profit and your bots. If you want the coin to go high - then just buy and stake. Wait for releases (here ofcourse the dev needs to do his job or else its bugger) - not news, but proper releases. Dev needs to stop posting pictures of whats it is going to be like and not release things untill something is really done. In the meanwhile the dev needs to do normal things like translations, WP, RM, exchanges etc etc etc. And dev - get the community involved in developing the coin.
That all if you people want the coin to succeed (my 2 cents - been in crypto since the begining....) - and btw - no other ways for coins to succeed but getting the commynity always involved and getting things done. As for panic buyers - then just relax, no one told you to invest - its your own choise, your fault only for buying when and what you did. No need to drive the price even lower by being an arse.
|
|
|
|
yes I noticed it too, the first wallet is keep buying....we are here, if it pump we're ready to ride..
And depend in what we consider a pump, if we're @2000 and go to 3000....yes it's a pump, maybe....
I want to knwo where's the guy that has bought 1.5BTC @3k yesterday...
I bought 1.2 btc for 2800 - 3000 sat yesterday |
|
|
|
|
anyone can come up with an accusation like this, whats your reason?
|
|
|
|
Looks like this one is going to the moon  I rekon 10 sats by tommorow |
|
|
|
Anyone at all?  |
|
|
|
|
file wallet.dat has LSN 82/686, past end of log at 1/476
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
file wallet.dat has LSN 1/611, past end of log at 1/476
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
file wallet.dat has LSN 82/686, past end of log at 1/1103
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 82/686 past current end-of-log of 1/1103
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 9
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
file wallet.dat has LSN 82/686, past end of log at 1/1730
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 82/686 past current end-of-log of 1/2022
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 9
PANIC: fatal region error detected; run recovery
wallet.dat: write failed for page 12
wallet.dat: unable to flush page: 12
DB_ENV->log_flush: LSN of 82/2259 past current end-of-log of 1/2022
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 17
txn_checkpoint: failed to flush the buffer cache: DB_RUNRECOVERY: Fatal error, run database recovery
PANIC: fatal region error detected; run recovery
Moving 82.200.205.55:52333 to tried
receive version message: version 32501, blocks=179471, us=109.235.185.115:4331, them=82.200.205.55:52333, peer=82.200.205.55:52333
trying connection 81.130.202.35:52333 lastseen=12,7hrs
connection timeout
trying connection 89.100.143.21:52333 lastseen=12,8hrs
connection timeout
trying connection 178.38.161.227:52333 lastseen=12,7hrs
connection timeout
trying connection 123.2.246.157:52333 lastseen=13,3hrs
connection timeout
trying connection 5.76.164.15:52333 lastseen=19,4hrs
GetMyExternalIP() received [109.235.185.115] 109.235.185.115:0
GetMyExternalIP() returned 109.235.185.115
AddLocal(109.235.185.115:52333,4)
connection timeout
trying connection 99.41.184.131:52333 lastseen=12,6hrs
connection timeout
trying connection 89.100.143.21:52333 lastseen=12,8hrs
connection timeout
trying connection 180.251.214.16:52333 lastseen=13,4hrs
connection timeout
trying connection 39.47.104.149:52333 lastseen=13,4hrs
connection timeout
trying connection 83.86.176.147:52333 lastseen=13,4hrs
connected 83.86.176.147:52333
send version message: version 70001, blocks=179471, us=109.235.185.115:52333, them=83.86.176.147:52333, peer=83.86.176.147:52333
Added time data, samples 8, offset -1 (+0 minutes)
Moving 83.86.176.147:52333 to tried
receive version message: version 32501, blocks=179471, us=109.235.185.115:4341, them=83.86.176.147:52333, peer=83.86.176.147:52333
trying connection 89.100.143.21:52333 lastseen=12,8hrs
Added 2 addresses from 83.86.176.147: 12 tried, 5678 new
connection timeout
trying connection 180.251.214.16:52333 lastseen=13,4hrs
connection timeout
trying connection 116.118.81.3:52333 lastseen=107,8hrs
connection timeout
trying connection 123.2.246.157:52333 lastseen=13,3hrs
connection timeout
trying connection 178.38.161.227:52333 lastseen=12,7hrs
NotifyKeyStoreStatusChanged
connection timeout
trying connection 78.50.144.201:52333 lastseen=10,7hrs
connection timeout
trying connection 64.156.193.100:52333 lastseen=10,6hrs
connected 64.156.193.100:52333
send version message: version 70001, blocks=179471, us=109.235.185.115:52333, them=64.156.193.100:52333, peer=64.156.193.100:52333
socket closed
disconnecting node 64.156.193.100:52333
trying connection 82.19.10.61:52333 lastseen=12,6hrs
connection timeout
trying connection 180.252.137.161:52333 lastseen=90,1hrs
|
|
|
|
Try the console app devcoind? tried... doesnt help |
|
|
|
Hey everyone. Does anyone know why i cant send any coins from my wallet? Every time i try to do so, windows says that the programm has shut down in an unsual way and it just shuts itself down.... whats the crack?  Which wallet version? 1.0.16 windows 32..... chain updates excellent and shows balance right and all transactions from 2 years back.... Anyone? Why does the wallet shut itself down when i try to move coins? I use the same version ill try it in a bit... did you try to delete your data folder (keeping your wallet.dat) and rescanning the blockchain? Yes tried everything.... same error - something about runtime and an usual closing.... Hmm works here.. windows 7 Any way of fixing this? - over 4 million coins stuck ((( |
|
|
|
|
Show Posts
