The old version worked.
I have uninstalled it and installed the new.
Now I get this message and do not know what to do:
NIS needs to be booted. Please open your wallet and boot a local node via the popup dialog or configure the auto-boot setting. (at block 396489). Any help?
Try this from the dropdown:  The user experience of NCC is being worked on by mix and rev (I think). At the moment it's suboptimal to say the least. |
|
|
|
hmmm update seems to be working, since this is a new version, does this mean I have to create a new back-up?
can't hurt but shouldn't be necessary. thanks! So my XEM are a mosaic now, that's cool, however I can't create new namespaces or mosaics yet is that right? I'm not 100% sure if NCC supports all of the functionality yet but NIS definitely does and so does the light wallet looking at the screenshots. |
|
|
|
hmmm update seems to be working, since this is a new version, does this mean I have to create a new back-up?
can't hurt but shouldn't be necessary. |
|
|
|
|
I'd like to point out that the light wallet supports brainwallets. So now there is no reason to store all your XEM at an exchange anymore because you wanna be "mobile".
Not that I actually believed that to be the reason for anyone to keep their XEM on an exchange but I wanted to point it out anyway.
The light wallet is still very much experimental but personally I'd encourage everyone that had problems with NCC to give it a bash. All you need is NIS. It serves the light wallet on port 7777.
You should be able to use the lightwallet on any NIS you know the address of without any security concerns. All signing is done in js on your local machine in your browser and no sensitve data travels over the wire. Of course people running their own NODEs can block that port if they don't like that.
Devs have done a really great job !
|
|
|
|
Can I upgrade by installing the NEM client from the official website?  Yes, but as usual I'd advise to remove the old version completely first. Trying a dirty install won't hurt though. |
|
|
|
Does anyone know why my Delegated harvesting stopped in November? I never stopped it, but the server i was connected to said it was full when i tried to connect to it again. I had never disconnected from the node, so unlsee the server went down at some point and someone else took my spot, i have no idea why.
Anyway i changed the host to 144.76.38.5 and it still has not harvested a single block all week.
I dont have to stop delegated harvesting every time i want to change a node do i? Im pretty sure ive never had to in the past.
TIA
Server stopped and restarted, you stop harvesting, unless you automate it. If you used someone else, they can kick you out. Run your own server and automate it to harvest. Yeah, I'm suprised there aren't more people complaining about this. You can't rely on servers not run by you. If you wanna make sure you are alway harvesting you have to run your own node. Yeah im aware of that, but why cant i harvest from the new node ive connected to? I will start a node myself once i get a raspberry Pi set up. Well appearantly it's full now. Maybe the node operator decided to not have other people harvest on it anymore. |
|
|
|
Does anyone know why my Delegated harvesting stopped in November? I never stopped it, but the server i was connected to said it was full when i tried to connect to it again. I had never disconnected from the node, so unlsee the server went down at some point and someone else took my spot, i have no idea why.
Anyway i changed the host to 144.76.38.5 and it still has not harvested a single block all week.
I dont have to stop delegated harvesting every time i want to change a node do i? Im pretty sure ive never had to in the past.
TIA
Server stopped and restarted, you stop harvesting, unless you automate it. If you used someone else, they can kick you out. Run your own server and automate it to harvest. Yeah, I'm suprised there aren't more people complaining about this. You can't rely on servers not run by you. If you wanna make sure you are alway harvesting you have to run your own node. |
|
|
|
What are the next steps in 2016 for the NEM-software?  Unless it happens today the very next steps will probably be the release of namespaces and mosaics to the mainnet |
|
|
|
They are the only two Im invested in. I won't be here pushing a different coin on the NEM thread, but it is truly THE Bitcoin killer. It has REALLY finally come. So if there is any way the NEM devs can think of a way to collaborate, this would be a wonderful idea. Maybe use some of their tech, and hook them up with some of your connections? Maybe not. IDK But I really love you both. Anyway, back to NEM There isn't going to be just one, so my bets are on NEM making it very far regardless. You will always have my support. I always knew Makoto would strike gold sooner or later, with all the meetings hes been going on for what seems like forever. Now he found some gold in his pan, so you know what happens next in the story.  As far as I remember IOTA stated literally in their first post that it isn't even supposed to be a competitor of BTC. It's directed at a completely different market, a market in which BTC doesn't stand a chance because of it's tech limits. So saying it's THE BTC killer is a tad ignorant imho. No offense. It's certainly an interesting project though. |
|
|
|
how come there is no node active atm ? is there a major update ? or what?
There are nodes active. Must be a configuration problem on your end. Port 7890 blocked ? visiting the http://www.nodeexplorer.com/ no node activity but at http://chain.nem.ninja/#/nodes/ there are few active nodes currently online. You're right, must be a problem with nodeexplorer.com. >70 is imho more than a few. Not enough but more than a few. |
|
|
|
how come there is no node active atm ? is there a major update ? or what?
There are nodes active. Must be a configuration problem on your end. Port 7890 blocked ? |
|
|
|
How many coins in total?
50 000 000 coins in the first block. Been answered like 3 times now one of which was like 5 posts abve yours |
|
|
|
A little more (and when I say little I actually mean a lot ) more technical details would be much appreciated. How do all nodes agree on the "line" i.e. the order in which nodes are supposed to forge ? How is the "evaluated score of credibility" calculated ? How did you solve the DDoS problem (assuming the entire networks knows which node is going to forge next) ? How (and who) is determined if and when "a node is fully operational" ? Any pre-requisites for nodes to join "the line" like a bond or anything ? ... Srsly you couldn't have been more vague  1) ... An important fact is that each time a node loses connection to the network, it internal memory is wiped, thus repeating the process at connection. ... 2) ... until the time elapses and every node calculates its score. ... 3) ... it will still be in vain, thanks to node.js millions of connections per sec can be handled with ease ... ... the network will just switch to the next one in line. ... First of all thank you for answering my questions ! I'm hoping there will be a detailed whitepaper or technical reference released that will detail everything ? @1) How are you going to force nodes to wipe their internal memory ? I'm assuming at some point this project will be open-source at which point you can't assume nodes to behave like you want them to. Also what if the node fails to forge a block ? Is there some punishment for that ? Lastly I'm not convinced that all nodes will come to the same conclusions for a new node that joins the network. Latencies will be different for each node, potentially very different once the network get's bigger. So a node might be pending for one node but activer for another. How does the conensus on that internal ledger of nodes work exactly ? @2) From how I understood it there is an internal ledger that all participating nodes agree on that defines the line. Now what stops any node from calculating the scores based on that ledger ? Every node has to be able to do that otherwise they can't know who's block they are supposed to accept or am I missing something here ? @3) So what you're saying is node.js solves the DDOS problem all by itself because it supports so many connections ? I'm sorry but I think that's a little delusional. Yes of course the network will swtich to the next one in line and so will the attacker. Is there any mechanism that will blacklist nodes that behave negatively ? |
|
|
|
A little more (and when I say little I actually mean a lot ) more technical details would be much appreciated. How do all nodes agree on the "line" i.e. the order in which nodes are supposed to forge ? How is the "evaluated score of credibility" calculated ? How did you solve the DDoS problem (assuming the entire networks knows which node is going to forge next) ? How (and who) is determined if and when "a node is fully operational" ? Any pre-requisites for nodes to join "the line" like a bond or anything ? ... Srsly you couldn't have been more vague |
|
|
|
When will there be a new minor version?
0.6.4x is the most current version since months.
is there a development progress anyway?
It won't be a minor version is my guess. All the bigger additions are on testnet for over a month or even 2 now. Better safe then sorry. I wanna say "fuck you" for implying that there is no dev progress at all but I'll refrain from it since we're so close to christmas. |
|
|
|
This coin is going nowhere with any of Silks guidance. Our only hope for this coin would be someone completely buying out the idea. I don't think Silk knows much, or anything at all about business. I offered to fix the site for free on multiple occasions but this dumbass is too preoccupied to even email me back. We have the shittiest exchanges imaginable, with no effort on Silk's part to expand. I'm done, I give up. Thank you Silk for wasting hundreds of my dollars. I know some people here are trying to boost the morale to protect their investment, but its done. This is going nowhere. Sell your coins and get out while you can. SILK WILL NEVER BE A SUCCESSFUL LEADER OF THIS PROJECT!
I saw your PM. I wrote earlier that I bring to the project in the hands of young guy who will direct the project, more than 70% of the code was studied. Now he is studying compiling windows clients, most likely in early 2016 a project will be fully under his leadership. Yes I admit that I'm not a good leader, I am well programmed , but the community needs a good leader who will know and the software code, I hope my assistant. I think the community will find him a good language. Maybe in the meantime you can work on a proper whitepaper that finally explains why you don't need new blocks even if there are no tx, how the network can confirm tx so fast and what the network topology looks like ? I mean were still unclear about the technology yet it's really the only thing that keeps people around. If that turns out to be flawed you can bring in 10 young guys and it won't do any good. |
|
|
|
Fuseleer what I was able to solve with my design (that turns PoW on its head so to speak) is transaction verification is as fast as propagating a transaction to a server and it propagating back out its confirmation. So roughly less than 1 second latency (can be faster but just referring roughly general case here).
But in terms of throughput, I believe the limiting factor (but not proven on a testnet yet) will be the rate of processing transactions on the CPU.
But we can talk about none of this without qualifying with detailed analysis of the security tradeoffs.
Thus it is useless to have these discussions and quote these figures until complete specifications and open source are revealed.
Thus I will not participate in any discussion on this until that juncture.
Is there any sort of timeline for your project or paper ? I really do not mean to offend. I'd just like to get a feel for when we're going to see actual results there. |
|
|
|
Updating ... My last version was: 0.6.25-BETA Current seems to be 0.6.43 Is the upgrade mandatory? Is there any danger in (not) upgrading? Where do I find a manual for that? How to upgrade on Debian? This manual only mentions "0.5.19 or lower", and not Linux. Just delete the old files, unpack the new files? suggestion: better documentation locallyWhat about adding a history.txt or changelog.txt to all nemwallet-folders. Where can I read a changelog? Thx. There is a category for that on the forum https://forum.nem.io/c/releaseSince those have been automatically migrated from the old froum some of them might look wonky but the information you're looking for will be there. I'm pretty sure there was at least 1 hardfork since .25 but even if not...why would you not want to upgrade ? Everything that you might need to do or that could go wrong should be here http://blog.nem.io/nem-tutorial-list/ |
|
|
|
Right, but I think I need invitation. Where I can get one? auto-invite is currently down. If you pm me an email address I'll add you. |
|
|
|
This is just a hype based on actually nothing... Price will drop again...
of course it will drop. duh! saying it's based on nothing is just bullshit. butthurt because you dumped early ? |
|
|
|
|
Show Posts
