Looking forward to the updates and fixes coming. Will look forward to the future of this coin and am sure it will take off with the current devs behind it. I have plenty o ideas and inspiration to add to features will get them shot over the next few days or over weekend when I get chance too  Thank you crazy! If it was not for this community we wouldn't be where we are. No problem I am in a way 1 problem solver and idea maker or as they call it an inivator to make things better than currently are Quick question is current block 288549 correct chain now? as seems got no out dated block chain and seems all good at min. Yes caller, go ahead, you're on the air with the Halo! Thanks for tuning into your local OC forum. Hot coins, cold juice. Wake up with Raven, Soopy, and the Halo in the morning. Oh oh oh oh oh oh oh oh see. OC. https://www.youtube.com/watch?v=_mcKzDwm8_ohttps://www.youtube.com/watch?v=paWBC3hFd5cSorry, had a Family Guy moment. The second video is funnier.  We welcome your ideas. The current moving chain is on 290456+ Stay tuned. Thanks for the info I do now see it moving again but seems stuck once again. Hope you guys manage to resolve this problem in up coming fixes and have some feature to check what chain is the correct one and auto block any bad nodes that are sending wrong chain downloads in the future Current blocks 288549 Wont update past Estimated blocks 290456 What I had to do was use 1.0.9 to get past 262799 and full synced. Then I used 2.0.0. I tried this from cryptoid's (edit: fairglu) post earlier and it sort of works. I had a lot of orphans but a lot of confirmed stakes. I was experiencing strange wallet behavior like wallet not responding right before it staked and a long pause of the splash screen when at "done loading". This is why I'm not sure if my stakes will actually be there in the new client. I suggest waiting for 2.0.1. It may be right around the corner. Halo you were explaining the situation I am and soon as I get home will solve. Do we use the 265k dump? |
|
|
|
old coin or new coin, write coin launch 2014 but tread starter post 30 august 2015
Thank you! I will do over at Bitcoingarden (Plug) Edit: Sorry. But It is stated in the timeline: April 27, 2014 Official launch. v1.0.0 released. Also: August 30, 2015 New thread is created. Cheers! -Raven |
|
|
|
Looking forward to the updates and fixes coming. Will look forward to the future of this coin and am sure it will take off with the current devs behind it. I have plenty o ideas and inspiration to add to features will get them shot over the next few days or over weekend when I get chance too Thank you crazy! If it was not for this community we wouldn't be where we are. No problem I am in a way 1 problem solver and idea maker or as they call it an inivator to make things better than currently are Quick question is current block 288549 correct chain now? as seems got no out dated block chain and seems all good at min. Yes caller, go ahead, you're on the air with the Halo! Thanks for tuning into your local OC forum. Hot coins, cold juice. Wake up with Raven, Soopy, and the Halo in the morning. Oh oh oh oh oh oh oh oh see. OC. https://www.youtube.com/watch?v=_mcKzDwm8_ohttps://www.youtube.com/watch?v=paWBC3hFd5cSorry, had a Family Guy moment. The second video is funnier. We welcome your ideas. The current moving chain is on 290456+ Stay tuned. Haha haha I love it!! |
|
|
|
Looking forward to the updates and fixes coming. Will look forward to the future of this coin and am sure it will take off with the current devs behind it. I have plenty o ideas and inspiration to add to features will get them shot over the next few days or over weekend when I get chance too Thank you crazy! If it was not for this community we wouldn't be where we are. No problem I am in a way 1 problem solver and idea maker or as they call it an inivator to make things better than currently are Quick question is current block 288549 correct chain now? as seems got no out dated block chain and seems all good at min. If people finally got their modes updated maybe... I am on the way home. I will check. |
|
|
|
Looking forward to the updates and fixes coming. Will look forward to the future of this coin and am sure it will take off with the current devs behind it. I have plenty o ideas and inspiration to add to features will get them shot over the next few days or over weekend when I get chance too Thank you crazy! If it was not for this community we wouldn't be where we are. |
|
|
|
This is hypothetical right now, but I had a thought I'd like to share: Everyone should be forewarned that some stakes may or may not orphan when the new client comes out. Time in question for the orphans would be from block 262799 and on, moreso around whatever block when 2.0.0 was released on August 29. Just be prepared for anything when the new release comes out, all I'm saying. Backing up your wallet.dat is advised, as you all should have been doing anyway. I would keep previous wallet.dat's as well, just in case. Cheers! Thanks halo for the update! |
|
|
|
Last year I bought some orange coins and then sold them.Now I see soopy's involement in this coin so I am in once again.This coin will surely rock in near future after fixing of the issues.
Thank you for the kind words! Get juiced! |
|
|
|
Hey all. I updated to 2.0, and I have been stuck on syncing since yesterday; 5294 blocks remaining. Do I need to do any other updates?
Still stuck. Can somebody please explain the steps I need to take to get my updated 2.0 working? Thanks Wow... even worse than before. I have 2.0 running. I redownloaded the 265k pre 2.0 bootstrap. Config is: rpcuser=username rpcpassword=password rpcallowip=127.0.0.1 daemon=1 server=1 listen=1 port=18872 rpcport=18873 addnode=orangecoinseednode1.no-ip.org addnode=orangecoinseednode2.no-ip.org addnode=orangecoinseednode3.no-ip.org addnode=orangecoinseednode4.no-ip.org addnode=orangecoinseednode5.no-ip.org addnode=75.130.163.51:18872 addnode=92.19.22.234:18872 addnode=50.188.13.41:18872 addnode=149.202.102.73:18872 and now, instead of being stuck on 5294 blocks remaining, I'm stuck on 23,298 blocks remaining... Go to https://chainz.cryptoid.info/oc/#!network. Under "Version, Protocol & Network Share", click "node list" for /OrangeCoin:2.0.0/. Copy all the nodes that are shown in the page that pops up and add these nodes to your orangecoin.conf . Close your wallet, then open it again to sync. John have you ever done a getpeerinfo from your console? There ARE 1.0.9's still, we need a "ban" on old versions or as suggested by crazyearner: "An Auto updater service" to force update message. Or we could "else if" in a version check from the client check in the chain itself (kind of like a manual getpeerinfo but automated AND WITH BANHAMMER!). Just a thought I have been thinking about. |
|
|
|
So I have helped secco over at BTCgarden, he's synced: That link is the 286 Chain, I should've made a Bootstrap but I stopped because of testing. But here's another update from secco! Quote from: raven7886 on Today at 10:33:57 PM
Glad I could help! Still syncing?
No, it worked. I'm up to date now. After copying the 285K chain, it just took 5 minutes to finish. THIS IS GOOD NEWS! Just got home from work, my getblockcount is: 288536 |
|
|
|
Hey all. I updated to 2.0, and I have been stuck on syncing since yesterday; 5294 blocks remaining. Do I need to do any other updates?
Still stuck. Can somebody please explain the steps I need to take to get my updated 2.0 working? Thanks Wow... even worse than before. I have 2.0 running. I redownloaded the 265k pre 2.0 bootstrap. Config is: rpcuser=username rpcpassword=password rpcallowip=127.0.0.1 daemon=1 server=1 listen=1 port=18872 rpcport=18873 addnode=orangecoinseednode1.no-ip.org addnode=orangecoinseednode2.no-ip.org addnode=orangecoinseednode3.no-ip.org addnode=orangecoinseednode4.no-ip.org addnode=orangecoinseednode5.no-ip.org addnode=75.130.163.51:18872 addnode=92.19.22.234:18872 addnode=50.188.13.41:18872 addnode=149.202.102.73:18872 and now, instead of being stuck on 5294 blocks remaining, I'm stuck on 23,298 blocks remaining... Go to https://chainz.cryptoid.info/oc/#!network. Under "Version, Protocol & Network Share", click "node list" for /OrangeCoin:2.0.0/. Copy all the nodes that are shown in the page that pops up and add these nodes to your orangecoin.conf . Close your wallet, then open it again to sync. worse yet... 23,304 remaining. Also, my OC balance is showing only around 1/10th of what it should be Your coins are safe. We just need to get you some more blocks they will reappear. |
|
|
|
Go to https://chainz.cryptoid.info/oc/#!network. Under "Version, Protocol & Network Share", click "node list" for /OrangeCoin:2.0.0/. Copy tall the nodes that are shown in the page that pops up and add these nodes to your orangecoin.conf . Close your wallet, then open it again to sync. Also, you client may show that it is out of sync but if you match the block explorer then you are in sync and on the correct chain. Right now my wallet shows that is it 1214 blocks behind but I"m in sync with the block explorer at block height of 288536. So if you are on the block block at the block explorer you are on the correct chain. Yeah huge bug in wallet. Says not synced, no green bar. But a checkmark is there. On current block.... Caused me to restart several times thinking I had a problem. But in the background it is still fighting the other chain.. . |
|
|
|
Can only wait and see if devs can provide some light on the matter. Maybe to make force and update though to old wallets to announce new wallet download and release. Feature for the future. Wallet updater. On loading wallet has little feature to check current version and also announce and a small popup saying update available download and update gives option to close or update. When clicking update launches command to close wallet and update services in background and then pop back up and run client after update with another one saying successful That way users would get updates a lot quicker too:) Nice! That's what we need! Community ideas! Cheers! -Raven Raven, I would forward that great idea to soopy if I were you . Sent PM, do we have an API for the version check? |
|
|
|
Can only wait and see if devs can provide some light on the matter. Maybe to make force and update though to old wallets to announce new wallet download and release. Feature for the future. Wallet updater. On loading wallet has little feature to check current version and also announce and a small popup saying update available download and update gives option to close or update. When clicking update launches command to close wallet and update services in background and then pop back up and run client after update with another one saying successful That way users would get updates a lot quicker too:) Nice! That's what we need! Community ideas! Cheers! -Raven |
|
|
|
|
I have that same entry on mine so and it JUST came up with the SYNC bar, I didnt have a SYNC bar for a few hours...
|
|
|
|
Well updated to latest wallet and was up to date and now today after not running for 24/48 hours. Closed and re opened client a number of times and it will not update currently stuck block 287972. 541 blocks remaining and not downloading yet have 11 active connections using most resent nodes. Any ideas to resolve this ?
you can create a batch file and have it look like this: "OrangeCoin-Qt.exe -debugnet" <!!!!!---- JUST THAT TEXT WITHOUT QUOTES! And then keep an eye on the debug.log in the %appdata% folder Pm me the tail end of it like 25-50 lines (notepad2 helps with numbering) |
|
|
|
Checking in for block: 288513 generated an hour ago... Hey all. I updated to 2.0, and I have been stuck on syncing since yesterday; 5294 blocks remaining. Do I need to do any other updates?
Still stuck. Can somebody please explain the steps I need to take to get my updated 2.0 working? Thanks I Had this issue. I stopped the wallet and restarted a few times. ALSO MAKE SURE TO ONLY USE OP THREAD NODES! I was using Chainz node list there's still spoofed chains within the list meaning 1.0.9 versions thinking they're on the 2.0 chain thus causes confusion to the client. Here's my CONF if you want to replicate the settings: EDIT: COPIED PASTED TEXT FROM CLIP ON PHONE! FOR INVESTIGATION!
This is my CONF:
port=18872
addnode=orangecoinseednode1.no-ip.org
addnode=orangecoinseednode2.no-ip.org
addnode=orangecoinseednode3.no-ip.org
addnode=orangecoinseednode4.no-ip.org
addnode=orangecoinseednode5.no-ip.org
addnode=75.130.163.51:18872
addnode=92.19.22.234:18872
addnode=50.188.13.41:18872
addnode=149.202.102.73:18872 ALSO: HOW IS THIS PERSON ABLE TO CONNECT AND STILL 1.0.9! Details:addr" : "93.123.163.96:18872", "services" : "00000001", "lastsend" : 1441143202, "lastrecv" : 1441144269, "conntime" : 1441119184, "version" : 60604, "subver" : "/OrangeCoin:1.0.9/", "inbound" : false, "releasetime" : 0, "startingheight" : 289031, "banscore" : 0 Not even on my list! I am going to give them a banscore! If they do not update! But inbound is false so we shouldn't have anything coming from him... If I understand correctly about inbounds true or false. Pleae let me know if you need ANY HELP. I also have a chain downloaded\bootstrap for 286K of blocks. Again please let me know, send me a PM or twat @rfarrow7886 Cheers! -Raven |
|
|
|
 By the way, I'm doing sync testing for soopy. I cannot provide any current block stats.
|
|
|
|
I have been getting a few blocks on v2 for the last hours, are these on the right fork? (this includes blocks mined by rich list list #12 and #9, so if it's a fork, they would be on it as well) Appreciating your thoughts on risks , but this was actually provided by the development team and if you cannot trust the development team , I do not know who you will. Technically speaking, the file is not provided by the team, but by a link to a mediafire url. The trust issue is not about the dev team, but about whether the data you get may or may not actually be from the dev team The github source code is trustable, as it is hosted on an https server, with a well identified url and a list of recent changes/commit and git's own tamper-proof hashing, so any hijacking attempt would not go unnoticed, but the mediafire link on the other hand is "meaningless", http, and the data itself hosted by a 3rd party. This is vulnerable to several vectors of attack. When replacing the db, the wallet will only check the last 2500 blocks, while when using a bootstrap.dat, the wallet will check the whole blockchain, making hijacking attempts as hard as a full-scale 51% attack, so it's okay to host the bootstrap.dat anywhere. The blockchain download will be coming off the website once we sort out our issues, bootstraps will take the place. I hated having to put the full db up because it isn't how crypto was meant to flow, but it's what worked at the time. We were dev-less, and I had to do what I had to do to keep the chain alive in my position. I've stated I attempted to make bootstraps in the past, they didn't work out. We have bootstrap capabilities now, so downloading those from mediafire shouldn't be an issue as you stated. So that obviously helped yesterday with the bootstrap command, Cheers! |
|
|
|
|
Show Posts
