If the coordinator node is only needed for the first year then can we expect the transaction times to go back to a few seconds after the first year, when the PoW is more robust?
Yes.
/thumbs up
good work sir!
Topic: IOTA - page 528. (Read 1473405 times)
If the coordinator node is only needed for the first year then can we expect the transaction times to go back to a few seconds after the first year, when the PoW is more robust?
Yes.
yes, yes. The network is still small, not much PoW, it would be vulnerable if not centralized at this stage (like any other decentralized network). That's why there will be a coordinator node for approx. 1 year that suggests regular nodes which tips of the tangle to extend. If you don't want this temporary centralization, you can change the ip address of the coordinator and replace it with an address of a node of your choice in the config file.
Higher centralization = higher vulnerability. We had to reduce the influence of the coordinator, now the nodes decide themselves which tips to extend. The coordinator suggests a general direction now instead of ordering which tips exactly should be extended. This has a drawback - confirmation time has increased from few seconds to few minutes - but it's more realistic.
The developers can't take the network down, "shouldn't work" = "new transfers shouldn't confirm if your node is in the coordinated mode".
If the coordinator node is only needed for the first year then can we expect the transaction times to go back to a few seconds after the first year, when the PoW is more robust?
yes, yes. The network is still small, not much PoW, it would be vulnerable if not centralized at this stage (like any other decentralized network). That's why there will be a coordinator node for approx. 1 year that suggests regular nodes which tips of the tangle to extend. If you don't want this temporary centralization, you can change the ip address of the coordinator and replace it with an address of a node of your choice in the config file.
Higher centralization = higher vulnerability. We had to reduce the influence of the coordinator, now the nodes decide themselves which tips to extend. The coordinator suggests a general direction now instead of ordering which tips exactly should be extended. This has a drawback - confirmation time has increased from few seconds to few minutes - but it's more realistic.
The developers can't take the network down, "shouldn't work" = "new transfers shouldn't confirm if your node is in the coordinated mode".
Quote
author=Come-from-Beyond Source: https://chat.iotatoken.com - #iotatesting]Iota network shouldn't work today and tomorrow
Is it so easy for developers to take down the network? Is the network still centralized in beta stage?
yes, yes. The network is still small, not much PoW, it would be vulnerable if not centralized at this stage (like any other decentralized network). That's why there will be a coordinator node for approx. 1 year that suggests regular nodes which tips of the tangle to extend. If you don't want this temporary centralization, you can change the ip address of the coordinator and replace it with an address of a node of your choice in the config file.
Quote
author=Come-from-Beyond Source: https://chat.iotatoken.com - #iotatesting]Iota network shouldn't work today and tomorrow
Is it so easy for developers to take down the network? Is the network still centralized in beta stage?
Short update:
The release date announcement is forced to be pushed back until tomorrow due to testing.
The release date announcement is forced to be pushed back until tomorrow due to testing.
Thank you so much!
Hopefully Monday will bring to us very good news!
As well, - if a week beginning from the good news - all week will be very good!
Cheers.
You made me blush! Really, I got on your list? That's surprising to hear.
Well, only trolls with such low IQ that they are unable to entertain me are included into the list...
Damn..that's harsh man
But all in good humour, I'm sure
Yeah, no worries, it's all good. My entertainment value - not so much. Being helpful - I try.
I am a long time CfB fan. Most of us are here because we recognize his genius and just want to be on that same ship.
You made me blush! Really, I got on your list? That's surprising to hear.
Well, only trolls with such low IQ that they are unable to entertain me are included into the list...
Damn..that's harsh man
But all in good humour, I'm sure
You made me blush! Really, I got on your list? That's surprising to hear.
Well, only trolls with such low IQ that they are unable to entertain me are included into the list...
@KimNg
I had you in my ignore list which is pretty short - just 3 entries. Do you know why I put you there? I can't recall that.
I had you in my ignore list which is pretty short - just 3 entries. Do you know why I put you there? I can't recall that.
You made me blush! Really, I got on your list? That's surprising to hear.
Some of my older non-IOTA posts might be interpreted as trolling, and who here hasn't done a little of that?
I am not a trader, so nothing is gained by causing a pump. I'm in this for the long-term.
Natural growth that is slow and steady combined with the buy and hold strategies of Warren Buffett and John Bogle work pretty well.
In my opinion bitcoin will eventually be dethroned by superior technologies, like blockchain 2.0 platforms and the new tangle.
For the most part I am a lurker, these are just my public service announcements.
I wanted to create my first IOTA address. By running the jar I am getting a BindException.
IRI 0.9.19
java.net.BindException: Permission denied
at java.net.PlainDatagramSocketImpl.bind0(Native Method)
at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:94)
at java.net.DatagramSocket.bind(DatagramSocket.java:392)
at java.net.DatagramSocket.(DatagramSocket.java:242)
at java.net.DatagramSocket.(DatagramSocket.java:299)
at java.net.DatagramSocket.(DatagramSocket.java:271)
at iri.Node.launch(Node.java:38)
at iri.IRI.main(IRI.java:44)
Flushing transactions chunk #0
Flushing transactions chunk #1
Flushing addresses chunk #0
Flushing addresses chunk #1
Flushing digests chunk #0
Flushing digests chunk #1
IRI 0.9.19
java.net.BindException: Permission denied
at java.net.PlainDatagramSocketImpl.bind0(Native Method)
at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:94)
at java.net.DatagramSocket.bind(DatagramSocket.java:392)
at java.net.DatagramSocket.
at java.net.DatagramSocket.
at java.net.DatagramSocket.
at iri.Node.launch(Node.java:38)
at iri.IRI.main(IRI.java:44)
Flushing transactions chunk #0
Flushing transactions chunk #1
Flushing addresses chunk #0
Flushing addresses chunk #1
Flushing digests chunk #0
Flushing digests chunk #1
Had the same issue on my first try, it happens because you have to instance running at the same time. Kill javaw.exe or restart your computer
I wanted to create my first IOTA address. By running the jar I am getting a BindException.
IRI 0.9.19
java.net.BindException: Permission denied
at java.net.PlainDatagramSocketImpl.bind0(Native Method)
at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:94)
at java.net.DatagramSocket.bind(DatagramSocket.java:392)
at java.net.DatagramSocket.(DatagramSocket.java:242)
at java.net.DatagramSocket.(DatagramSocket.java:299)
at java.net.DatagramSocket.(DatagramSocket.java:271)
at iri.Node.launch(Node.java:38)
at iri.IRI.main(IRI.java:44)
Flushing transactions chunk #0
Flushing transactions chunk #1
Flushing addresses chunk #0
Flushing addresses chunk #1
Flushing digests chunk #0
Flushing digests chunk #1
IRI 0.9.19
java.net.BindException: Permission denied
at java.net.PlainDatagramSocketImpl.bind0(Native Method)
at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:94)
at java.net.DatagramSocket.bind(DatagramSocket.java:392)
at java.net.DatagramSocket.
at java.net.DatagramSocket.
at java.net.DatagramSocket.
at iri.Node.launch(Node.java:38)
at iri.IRI.main(IRI.java:44)
Flushing transactions chunk #0
Flushing transactions chunk #1
Flushing addresses chunk #0
Flushing addresses chunk #1
Flushing digests chunk #0
Flushing digests chunk #1
is there a trusted web wallet for claiming?
As far as I understand there will be never any "web wallet" in IOTA, cause it is obsolete technology from the age of blockchains and Bitcoin and in IOTA you do not need the full tangle snapshot to make transactions.
Concerning claiming, the network is stopped until mondey. On mondey you can claim in your localwallet (and I hope you will donate to foundation)
. Can someone refer me to where I can see the new total adjusted supply of iotas. Thanks.
I don't remember the exact amount but it's (3^33-1)/2.
I bet Jinn's price will keep going up after the official release of iota and the launch of Jinn's website.
Or down, depends on the news that will be published.
Jump to: