AURORACOIN - Empowering Financial Freedom

[LTEX]

For those wondering why I'm such a strong believer in this initiative, you should take some time to read this article:

http://guardianlv.com/2013/12/icelanders-overthrow-government-and-rewrite-constitution-after-banking-fraud-no-word-from-us-media/

Maybe then you see how special this little northern country actually is and how logical it is that this is the ideal breading ground for a successful adoption of cryptocurrencies...

[1714050728]

1714050728

[1714050728]

1714050728

[1714050728]

1714050728

[flound1129]

I just received an email about a new client, is there a new client?  If so please publish this information via official channels.

[BioMike]

A new wallet has been released on 17 August 2015: http://auroracoin.is/

Please update.

[ny2cafuse]

In case you missed the original post, here it is again:

NEW OSX and Windows Wallets are released!







You can download them @ http://auroracoin.is

Direct download links:

Windows Wallet
Mac Wallet


This is the first of a series of new releases you can expect from your development team in the next few weeks. We expect the IOS wallet (that can be tested as stated by LTEX a few posts above) to be released in the App Store soon. Although it's very hard to pinpoint any exact dates, please have a look at our roadmap to see what we have in store...

[flound1129]

Is this new wallet a hardfork or is a hardfork planned in the near future?

[molecular]

Is it problematic to keep my blockexplorer on an older version (1.03) or do I have to update? What exactly are the changes from a pure node point of view (no wallet)?

[ny2cafuse]

Is this new wallet a hardfork or is a hardfork planned in the near future?

This was pushed out more as a soft fork.  The code is in place to restrict the connections to newer versions, but no code has been changed that will invalidate old wallet block creation.  At this time, there is a bridge node connecting the network and keeping everything in sync.  The next wallet update will most likely require a hard fork.  Possible changes to the next version's code are still in being SWOT'd.

Is it problematic to keep my blockexplorer on an older version (1.03) or do I have to update? What exactly are the changes from a pure node point of view (no wallet)?

There are no changes in algos, timing, or anything else.  This release was more of an overdue update to the wallet version.  Your explorer will still function until we update the bridge node.  We won't update the bridge node until we're sure all the services have updated to the new wallet, and it's safe to cut off the old wallets.

I would suggest updating to be safe.

-Fuse

[BioMike]

Past few weeks I've been working on software to track the health of our seed nodes. Today we hooked up all the seed nodes to this new monitoring system. People can see the status of our seeds at http://seeds.auroracoin.is

The software for this monitoring system has been made free under the GNU Affero General Public License so other cryptocoins can use this software as well and collaborate in improving the system.

Source: https://github.com/BioMike/seed-node-monitor

If people are wondering which node is the bridge node, its "USA West", visible due to the high amount of wallets which haven't been updated yet.

[molecular]

"bridge node"? Is this explained somewhere? What does it do and why is it necessary?

[ny2cafuse]

"bridge node"? Is this explained somewhere? What does it do and why is it necessary?

We operate a node that allows older wallets to communicate with the newer wallets.  The newer wallets block connections to from the old wallet via the minimum protocol version.  The US West node still allows the connections, effectively bridging the old clients with the new ones.  It's necessary to not cause a fork between the two versions while we get everyone updated.

Bridge node isn't necessarily the technical term(not sure if their is one), but it was about the best phrase I could come up with.  I guess you could call it the transitional node too.

-Fuse

[molecular]

"bridge node"? Is this explained somewhere? What does it do and why is it necessary?

We operate a node that allows older wallets to communicate with the newer wallets.  The newer wallets block connections to from the old wallet via the minimum protocol version.  The US West node still allows the connections, effectively bridging the old clients with the new ones.  It's necessary to not cause a fork between the two versions while we get everyone updated.

Bridge node isn't necessarily the technical term(not sure if their is one), but it was about the best phrase I could come up with.  I guess you could call it the transitional node too.

-Fuse

Excuse my irgnorance, but why do new nodes block connections from old nodes?

[BioMike]

"bridge node"? Is this explained somewhere? What does it do and why is it necessary?

We operate a node that allows older wallets to communicate with the newer wallets.  The newer wallets block connections to from the old wallet via the minimum protocol version.  The US West node still allows the connections, effectively bridging the old clients with the new ones.  It's necessary to not cause a fork between the two versions while we get everyone updated.

Bridge node isn't necessarily the technical term(not sure if their is one), but it was about the best phrase I could come up with.  I guess you could call it the transitional node too.

-Fuse

Excuse my irgnorance, but why do new nodes block connections from old nodes?

We want to get rid of the old wallets (so we can push notifications in the future when people need to update), we don't have the keys for the old wallets to do this. There will always be a few nodes that will never upgrade. We decided to restrict the connections between the old and new wallets to facilitate this and have a smoother chain fork in the future.

[LTEX]

Only hero members on this last page, looks like we're finally growing up 

[bram_vnl]

First time I see this coin

[flound1129]

We operate a node that allows older wallets to communicate with the newer wallets.  The newer wallets block connections to from the old wallet via the minimum protocol version.  The US West node still allows the connections, effectively bridging the old clients with the new ones.  It's necessary to not cause a fork between the two versions while we get everyone updated.

Bridge node isn't necessarily the technical term(not sure if their is one), but it was about the best phrase I could come up with.  I guess you could call it the transitional node too.

-Fuse

We want to get rid of the old wallets (so we can push notifications in the future when people need to update), we don't have the keys for the old wallets to do this. There will always be a few nodes that will never upgrade. We decided to restrict the connections between the old and new wallets to facilitate this and have a smoother chain fork in the future.

So this is a 'hostile takeover' of sorts?

[Skarfur]

So just to make you guys aware then we are moving the Auroracoin foundation funds around today.

The 1 mill was just sent from it's initial address to another address from which we will be sending 50k Auroracoin to 20 cold addresses. We will publish a list of these addresses and our plan for using these funds shortly.

[Bimmerhead]

We operate a node that allows older wallets to communicate with the newer wallets.  The newer wallets block connections to from the old wallet via the minimum protocol version.  The US West node still allows the connections, effectively bridging the old clients with the new ones.  It's necessary to not cause a fork between the two versions while we get everyone updated.

Bridge node isn't necessarily the technical term(not sure if their is one), but it was about the best phrase I could come up with.  I guess you could call it the transitional node too.

-Fuse

We want to get rid of the old wallets (so we can push notifications in the future when people need to update), we don't have the keys for the old wallets to do this. There will always be a few nodes that will never upgrade. We decided to restrict the connections between the old and new wallets to facilitate this and have a smoother chain fork in the future.

So this is a 'hostile takeover' of sorts?

No, this 'takeover' has the blessing of baldur who has pointed his auroracoin.org site to the new team's forum

[dinobotta]

No, this 'takeover' has the blessing of baldur who has pointed his auroracoin.org site to the new team's forum

Here is a link to Baldurs last words to the community https://www.reddit.com/r/auroracoin/comments/33iogi/aurburnaurburnaurburnaurburn7es4rf_balduro_a_man/.

"Special thanks to those who continue the project. Baldur"

[flound1129]

We operate a node that allows older wallets to communicate with the newer wallets.  The newer wallets block connections to from the old wallet via the minimum protocol version.  The US West node still allows the connections, effectively bridging the old clients with the new ones.  It's necessary to not cause a fork between the two versions while we get everyone updated.

Bridge node isn't necessarily the technical term(not sure if their is one), but it was about the best phrase I could come up with.  I guess you could call it the transitional node too.

-Fuse

We want to get rid of the old wallets (so we can push notifications in the future when people need to update), we don't have the keys for the old wallets to do this. There will always be a few nodes that will never upgrade. We decided to restrict the connections between the old and new wallets to facilitate this and have a smoother chain fork in the future.

So this is a 'hostile takeover' of sorts?

No, this 'takeover' has the blessing of baldur who has pointed his auroracoin.org site to the new team's forum

Why can't he give you the alert key then?  And the official Github?

[ny2cafuse]

Why can't he give you the alert key then?  And the official Github?

That would probably be a question better directed to Balduro.  I will say though that you will probably find out that he isn't open to direct communication now.  Our team reached out to him numerous times to try to square away a lot of those issues.  Not knocking Balduro... sometimes you just want to be left alone.

However, I'm sure you could understand now why we would want to change the alert keys with Balduro out of the picture.  Additionally, it's just easier to have the code in a github we control, rather than rely on keeping the project on an account of someone who has obviously stepped away from this project.

-Fuse