After any leeway time to upgrade, yes it should do, anything else should get dropped.
Okay great!  i know your dev has skills to fix the coin but he is doing it by... way i cannot tolerate. he have missed some important things, but i know he can fix those. just give him the time he needs.
just to say there is people who got help from my posts...
im not the guy who will want to fix your coin.
i could name a guy who could fix this up in no time..
Alright, fair enough. But then instead of making it look like BCR is going nowhere, why don't you give suggestions and eventually provide some constructive criticism? No offense but the only things I see coming from you are things you could do. Actions speak louder than words!  |
|
|
|
Don't forget all the ones listed in-wallet on the banknodes page.  Does it only show the nodes running the latest protocol version by default? |
|
|
|
Started/closed multiple times without any issues, working fine on Windows 8.1 x64 and Windows 10 x64! Are there any other nodes available? Synchronising is taking forever now. So far I used: addnode=146.90.136.80 Click on Nodelist https://chainz.cryptoid.info/bcr/#!networkThank you! For those wondering, here's the full list of active nodes on the latest protocol (70011): addnode=104.154.35.53 addnode=104.154.62.20 addnode=104.197.114.123 addnode=104.197.25.255 addnode=104.197.41.48 addnode=104.197.42.233 addnode=104.197.97.93 addnode=104.238.186.50 addnode=109.93.108.75 addnode=121.73.87.155 addnode=130.211.134.141 addnode=146.90.136.80 addnode=162.222.182.149 addnode=188.193.114.167 addnode=46.9.115.145 addnode=50.155.205.187 addnode=62.194.60.156 addnode=82.211.1.181 addnode=91.230.123.101 addnode=91.230.123.11 |
|
|
|
Started/closed multiple times without any issues, working fine on Windows 8.1 x64 and Windows 10 x64! Are there any other nodes available? Synchronising is taking forever now. So far I used: addnode=146.90.136.80 |
|
|
|
yes i will leave, i got all info needed.
i cannot recommend coin like this to people who prefer working platform.
ps. your laggin some very important things now, all of it is not just the source.
and alteast you have a hunt what i told earlier, </==
im not giving the answers directly.
Dude for real, what is your problem? You said the same shit a couple of times already. Stop pretending that the success and future of BCR is depending on your words or actions, because it surely isn't. Please leave this thread as this obviously isn't the place you belong. |
|
|
|
Progress. It's been slow but steady.
Over the weekend I created new builds for all systems. I will replace the old wallet with the new one now. Stay tuned. Seated first row to test on multiple x64 systems, let us know when they're replaced! Keep up the good work team! |
|
|
|
Very well done, my compliments! |
|
|
|
at 7 x64 it crashes after 15-30mins since chain is fully loaded,
What happens if you add the -debug parameter in the shortcut? I'm nearly 100% in-sync, will be doing some testing. |
|
|
|
|
I can confirm the latest wallet (v0.30.17.2-Win64) is crashing upon opening, even when started clean with an empty data folder.
EDIT:
Seems that starting the wallet with the -debug parameter starts it without issues on Windows 8.1 x64.
|
|
|
|
How are exchanges and traders affected by this? Let's hope the traded coins will not go to waste  |
|
|
|
Masternode “Start” Announcement/Reminder v12 !
Please do NOT use "masternode start" or "masternode start-many/alias" commands anymore to bump your node !!
This worked before, but now since v12 this will affect your node position quite the opposite way now. Use them only when you actually start new MN or MN that dropped out of list. You should not use this command if there is no additional announcement and/or no protocol bump mentioned because in usual cases MN will start automatically on daemon restart.
Some simple notes on what to do in case of some issues:
- If your daemon died but MN still in the list - just restart the daemon and check in next 5-10 minutes if it's still in the list.
- If your daemon died and MN dropped from the list on some site - that doesn't really mean 100% that it dropped on the whole network, could still be visible in some parts of network for another few minutes so just restart demon again and see if it reappear in next 5-10 minutes there. If not - no luck then, everyone kicked you out of list and you have to use "masternode start" or "masternode start-many/alias" and start from the end of payment queue again.
we have many many people asking the same question:
why are my MN's not getting paid since 7-10 days ?
Well, everybody made the same mistake as described above.
only use "start' when actually needed
Tx Udjin
bump, for those who are unaware |
|
|
|
So we're down to 3 days and we've had a phenomenal support from so many of you. We still have a ways to go, but that's not going to stop us from continuing to crank out code. Lootz from SuperNET Radio has contacted us again for another radio interview. We want to take this time to answer questions that you guys might still have about R3D. Once we have a nice list of questions stacked up we can schedule a time for us to go on the air with Lootz. Feel free to send your email questions to supernetradio@gmail.com. If you wish to remain anonymous please state that in your email. While I perfectly understand what R3D is and what it's all about, the people I told about R3D still had questions about what it exactly is that it offers. So apparently it's either still a bit vague/unclear or just hard to understand for the less tech-savvy. The question I would like to hear answered (for the less tech-savvy people) in the most plain English with as less jargon as possible: What is R3D and how does it work?Making sure everyone has a better understanding of what R3D is might bring new investors to the table. EDIT:Oops, missed the part where it said email your questions to SuperNET. Will still do that as we speak. Email sent to SuperNET! |
|
|
|
|
The latest wallet gets stuck synchronizing at block 189981, even after starting the wallet with the -reindex parameter. Also when I try to close the wallet it gets stuck at the "Closing the Bitcredit Core wallet..." message, I have to kill the process.
Any clues?
EDIT:
I removed the files inside the data folder and started the wallet again. Whilst having just 1 connection to the network it took a while (~1 hour) but it synchronized a bit further this time. However, I'm stuck again:
{
"version" : 301609,
"protocolversion" : 70008,
"walletversion" : 60000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 199999,
"timeoffset" : 0,
"moneysupply" : 19594284.99810301,
"connections" : 1,
"proxy" : "",
"difficulty" : 0.00001604,
"testnet" : false,
"keypoololdest" : 1440751523,
"keypoolsize" : 2,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
|
|
|
|
Hello Guys,
I was watching this thread very closely and was working beyond something greater that will benefit the Coin as well as you , the investors.
I was working on implementing the BIP Protocols on the NavajoCoin blockchain , you will be able to see its progress on our Official Github in a few hours , now please do keep in mind that this work is very very complicated and complex and mind you , we are the only ALTCOIN to have implemented this and not being a coin directly deriving from Bitcoin.
https://github.com/sherlockcoin/navajocoin/tree/BIP-Protocols (You can watch the updates being posted here as they are committed)
Let me outline the positive impacts due to these updates.
1 - Improved Web Wallet and Mobile Wallet Capability
2 - Deterministic Wallet Capability
3 - Hierarchical Deterministic Wallet Capability (HD WALLET)
4 - Custom Address Generation
5 - Faster and Secure blockchain Protocols.
I would like to mention again that this has been a very time consuming and a complex process that needed a lot of my attention and careful evaluation and integration from my end and this has taken up a lot of my time in doing the same.
Please do not take our work lightly as we do what we do with the love of it and take it very serious and do what we do the best.
I would also like to extinguish rumours about myself and OrangeCoin, I have and will always be the Core Developer of NavajoCoin and have and always given my utmost best and innovation for NavajoCoin like I m doing now. I m a Technical and Development Adviser as an individual and some individuals consult me , with related to development matters and I help them with what I know the best. You might have noticed this many many times in my life as a Developer and in the CryptoWorld. Before working on NAVAJOCOIN , I used to help a lot of 1st generation coins and their communities to get their coins back on track and helped them with their development matters as well as their core developers with my knowledge. So please do not fall for any rumours or related that say otherwise.
We have come a long way from our humble beginnings with NavajoCoin , from SummerCoin ---> SummerCoinV2 ----> NavajoCoin , we've been here for more than a year , we have faced the worst but came out stronger every single time and will continue to prosper for many many years to come.
Please bear with us.
My time is with NavajoCoin and yours.
Warm Regards,
~SoopY~ Thank you for the update, this was exactly what I - and others - needed. Now to prevent this from happening again, how about giving the community a Weekly Update regarding development progress, marketing, news, etc.? Doing so might attract new investors and create a more positive community vibe. About this BIP protocol, what exactly is it and how does NAV exactly benefit from it? From Wikipedia: Bearer Independent Protocol, a technology in mobile communication to provide the (U)SIM with access to data services through any of the data bearers supported by the mobile phone. |
|
|
|
Hey guys, soopy is finishing integrating BIP32, we'll post an update once that task is finished.
Best Regards
Strugg That's great and all, but any GitHub branch available where we can follow the development? |
|
|
|
Am i right in thinking that soopy is also the dev for orange coin too? Might explain the delays and radio silence  I didn't even know about OC but It seems a new (unknown) den has taken over the project Greedyjohn has been frequenting their thread (and I haven't seen him around this one) for a while, promoting OC They advertise anon transactions and masternodes! NAV has suffered delay upon delay and lately barely gets even progress reports. This proves nothing but should be enough to get anyone thinking. Any comments from the dev team, or even better progress reports? Your thoughts were exactly what i was concluding……. We will probably be told to stop fudding and have our posts deleted but as I hold over 1 million Nav and have donated to the devs numerous times it would be nice to know whats going on. Exactly, +1 on that. An active development team should always keep in touch with the community and keep them us to date. But what's there to tell if there's no development going on, right..? |
|
|
|
Nice work, good job! Working fine on Windows 8.1 x64 and Windows 10 x64. Dragos, could you help me setup my Windows build environment? |
|
|
|
Tired of c++ and python.... so for now i'll be trying my hand at building our QT wallet for use on android. Maybe tinker with the exchange a little.
Anyone wanna try a windows build on the dev branch? Maybe Mac too, i'll give you 20K BCR for each
I'm trying my best in setting up a build environment for Windows. Reading through several guides as this is new to me. Any help is welcome! |
|
|
|
|
Show Posts
