[ANN] AMP - The Currency That Powers Your Attention On Synereo

[fartbags]

The main thing I want from a PoS coin is the ability to stake while my coins are in a cold wallet.

Nxt can do that by leasing the forging (=staking) power to another account.

That's a great idea. People need cold storage.

[1713563528]

1713563528

[1713563528]

1713563528

[1713563528]

1713563528

[1713563528]

1713563528

[fartbags]

The main thing I want from a PoS coin is the ability to stake while my coins are in a cold wallet.

Nxt can do that by leasing the forging (=staking) power to another account.

That's a great idea. People need cold storage.

NXT is built with java. Java is already used in Synereo. The NXT code might be a really good place to start for Synereo. I get a sense that Synereo really likes Java.

[DecentralizeEconomics]

NXT is built with java. Java is already used in Synereo. The NXT code might be a really good place to start for Synereo. I get a sense that Synereo really likes Java.

This is a good idea.  Here's the link to NXT's source -> https://bitbucket.org/JeanLucPicard/nxt/overview

[Elokane]

What specifically in the NXT code do you think could assist in our project?

[fartbags]

What specifically in the NXT code do you think could assist in our project?

Their PoS code. The most important feature of PoS for myself is the ability to sign an offline transaction and then bring that signed transaction onto the network so that it allows me to stake my coins that are stored offline in a paper wallet.

[retasdaf123]

All Bark, No bite,
All fart, no S**t
All Talk, No action.

Alot of people invested alot of money in this. We were expecting more than a link to some skype conferences once a week and the ability to set up your node.....
WHo cares about that!?
We want to see a finished product. or atleast some progress towards one.
How much money is left?
where have these fund been spent.
If its being spent on a salary for you guys to talk on skype once a week. this is a flat out scam.
we don;t care about your collaoration with ethereum. what does this even mean.
We care about ethereums collaborations with SYnereo -
 Come on Guys.
GET CODING, SHOW US SOMETHING!

[fartbags]

All Bark, No bite,
All fart, no S**t
All Talk, No action.

Alot of people invested alot of money in this. We were expecting more than a link to some skype conferences once a week and the ability to set up your node.....
WHo cares about that!?
We want to see a finished product. or atleast some progress towards one.
How much money is left?
where have these fund been spent.
If its being spent on a salary for you guys to talk on skype once a week. this is a flat out scam.
we don;t care about your collaoration with ethereum. what does this even mean.
We care about ethereums collaborations with SYnereo -
 Come on Guys.
GET CODING, SHOW US SOMETHING!

Where is the Synereo PoS blockchain code? SHow us something...

[leithaus]

All Bark, No bite,
All fart, no S**t
All Talk, No action.

Alot of people invested alot of money in this. We were expecting more than a link to some skype conferences once a week and the ability to set up your node.....
WHo cares about that!?
We want to see a finished product. or atleast some progress towards one.
How much money is left?
where have these fund been spent.
If its being spent on a salary for you guys to talk on skype once a week. this is a flat out scam.
we don;t care about your collaoration with ethereum. what does this even mean.
We care about ethereums collaborations with SYnereo -
 Come on Guys.
GET CODING, SHOW US SOMETHING!

Where is the Synereo PoS blockchain code? SHow us something...

Thanks for wanting to keep us accountable! We really appreciate it. In general, we do technical updates at the top of each community hangout for people who are not watching the repos and checkins directly. i know there are a lot and it's hard to keep track of all the repos and branches to be watching. That's part of the reason i give a technical update each week so that we are completely transparent and people can see exactly how we are spending the money and what progress we are making.

The progress on the core stack (see https://github.com/synereo ; more specifically basic content delivery mechanism: https://github.com/synereo/special-k ; cdn + user model: https://github.com/synereo/agent-service-ati-ia ; http trampoline: https://github.com/synereo/gloseval ; ui : https://github.com/synereo/agentui ) was first done in a sandbox repo (https://github.com/leithaus/strategies) where i pulled out the major messaging layer and upgraded this from RabbitMQ 2.6 to 3.5.5. This took a lot of work. There were breaking API changes, and more importantly, there were breaking changes to the configuration. So, even though it might look like there were only a few lines of code that changed, most of the work was in figuring out exactly which lines of code to change and then testing! This was moved back into the synereo main repo and i then moved on to updating the local storage. This was done a month ago. The docker work got a little hung up (somebody else was doing it and now i'm taking it over).

Making the node available via AMZN AMI is actually more of a big deal than you might imagine as there are many dependencies to manage, and by making it an AMI the community is not burdened with all of that management. It also takes time to test. This goes doubly for the docker work as there are many more moving parts.

We had Justin Long take a stab at a redesign of the UI/UX. That code is here (https://github.com/synereo/nuui). The feedback was universally that that was not a good direction to go, so we backtracked to the existing UI with a gap analysis to other social media. If you have strong opinions about the UI, please consider using what we've got and giving us some detailed feedback about what you would like to see done differently.

The work with the LivelyGig team is here (https://github.com/LivelyGig/Product) and the choice to switch from Haxe to scala.js has been long anticipated. In 2012 we attempted to use an earlier version of Scala to JS, but that failed because that compiler was simply too broken to work with. So, we backtracked to Haxe and were able to make some progress (again, see https://github.com/synereo/agentui). Now that scala.js is both stable and has a good team behind it, and we have the work from the LivelyGig team to demonstrate that you can connect scala.js + react to our backend stack, we are porting the the haxe codebase to that framework while improving the UI. So, now really is the time to give us detailed feedback about the UI.

Finally, as for the PoS code, as i have mentioned in the Synereo Community Hangouts, the code began here (https://github.com/leithaus/strategies/tree/casper/src/main/scala/com/synereo) and is now here (https://github.com/synereo/agent-service-ati-ia/tree/casper/AgentServices-Store/src/main/scala/com/protegra_ati/agentservices/protocols/consensus). The documentation is here (https://github.com/leithaus/casper).

Part of the reason we hold the Synereo Community Hangouts is so that i have one place i need to communicate all these updates. It would be (and actually is) a full time job tracking down every channel and keeping every subcommunity up-to-date on what we are doing. So, while it might seem we are only talking, if one actually listens, they will see that we are making a *huge* amount of progress given our resources.

[sidhujag]

All Bark, No bite,
All fart, no S**t
All Talk, No action.

Alot of people invested alot of money in this. We were expecting more than a link to some skype conferences once a week and the ability to set up your node.....
WHo cares about that!?
We want to see a finished product. or atleast some progress towards one.
How much money is left?
where have these fund been spent.
If its being spent on a salary for you guys to talk on skype once a week. this is a flat out scam.
we don;t care about your collaoration with ethereum. what does this even mean.
We care about ethereums collaborations with SYnereo -
 Come on Guys.
GET CODING, SHOW US SOMETHING!

Where is the Synereo PoS blockchain code? SHow us something...

Thanks for wanting to keep us accountable! We really appreciate it. In general, we do technical updates at the top of each community hangout for people who are not watching the repos and checkins directly. i know there are a lot and it's hard to keep track of all the repos and branches to be watching. That's part of the reason i give a technical update each week so that we are completely transparent and people can see exactly how we are spending the money and what progress we are making.

The progress on the core stack (see https://github.com/synereo; more specifically basic content delivery mechanism: https://github.com/synereo/special-k; cdn + user model: https://github.com/synereo/agent-service-ati-ia; http trampoline: https://github.com/synereo/gloseval; ui : https://github.com/synereo/agentui ) was first done in a sandbox repo (https://github.com/leithaus/strategies) where i pulled out the major messaging layer and upgraded this from RabbitMQ 2.6 to 3.5.5. This took a lot of work. There were breaking API changes, and more importantly, there were breaking changes to the configuration. So, even though it might look like there were only a few lines of code that changed, most of the work was in figuring out exactly which lines of code to change and then testing! This was moved back into the synereo main repo and i then moved on to updating the local storage. This was done a month ago. The docker work got a little hung up (somebody else was doing it and now i'm taking it over).

Making the node available via AMZN AMI is actually more of a big deal than you might imagine as there are many dependencies to manage, and by making it an AMI the community is not burdened with all of that management. It also takes time to test. This goes doubly for the docker work as there are many more moving parts.

We had Justin Long take a stab at a redesign of the UI/UX. That code is here (https://github.com/synereo/nuui). The feedback was universally that that was not a good direction to go, so we backtracked to the existing UI with a gap analysis to other social media. If you have strong opinions about the UI, please consider using what we've got and giving us some detailed feedback about what you would like to see done differently.

The work with the LivelyGig team is here (https://github.com/LivelyGig/Product) and the choice to switch from Haxe to scala.js has been long anticipated. In 2012 we attempted to use an earlier version of Scala to JS, but that failed because that compiler was simply too broken to work with. So, we backtracked to Haxe and were able to make some progress (again, see https://github.com/synereo/agentui). Now that scala.js is both stable and has a good team behind it, and we have the work from the LivelyGig team to demonstrate that you can connect scala.js + react to our backend stack, we are porting the the haxe codebase to that framework while improving the UI. So, now really is the time to give us detailed feedback about the UI.

Finally, as for the PoS code, as i have mentioned in the Synereo Community Hangouts, the code began here (https://github.com/leithaus/strategies/tree/casper/src/main/scala/com/synereo) and is now here (https://github.com/synereo/agent-service-ati-ia/tree/casper/AgentServices-Store/src/main/scala/com/protegra_ati/agentservices/protocols/consensus). The documentation is here (https://github.com/leithaus/casper).

Part of the reason we hold the Synereo Community Hangouts is so that i have one place i need to communicate all these updates. It would be (and actually is) a full time job tracking down every channel and keeping every subcommunity up-to-date on what we are doing. So, while it might seem we are only talking, if one actually listens, they will see that we are making a *huge* amount of progress given our resources.

Your first 3 github links are broken

[leithaus]

All Bark, No bite,
All fart, no S**t
All Talk, No action.

Alot of people invested alot of money in this. We were expecting more than a link to some skype conferences once a week and the ability to set up your node.....
WHo cares about that!?
We want to see a finished product. or atleast some progress towards one.
How much money is left?
where have these fund been spent.
If its being spent on a salary for you guys to talk on skype once a week. this is a flat out scam.
we don;t care about your collaoration with ethereum. what does this even mean.
We care about ethereums collaborations with SYnereo -
 Come on Guys.
GET CODING, SHOW US SOMETHING!

Where is the Synereo PoS blockchain code? SHow us something...

Thanks for wanting to keep us accountable! We really appreciate it. In general, we do technical updates at the top of each community hangout for people who are not watching the repos and checkins directly. i know there are a lot and it's hard to keep track of all the repos and branches to be watching. That's part of the reason i give a technical update each week so that we are completely transparent and people can see exactly how we are spending the money and what progress we are making.

The progress on the core stack (see https://github.com/synereo ; more specifically basic content delivery mechanism: https://github.com/synereo/special-k ; cdn + user model: https://github.com/synereo/agent-service-ati-ia ; http trampoline: https://github.com/synereo/gloseval ; ui : https://github.com/synereo/agentui ) was first done in a sandbox repo (https://github.com/leithaus/strategies) where i pulled out the major messaging layer and upgraded this from RabbitMQ 2.6 to 3.5.5. This took a lot of work. There were breaking API changes, and more importantly, there were breaking changes to the configuration. So, even though it might look like there were only a few lines of code that changed, most of the work was in figuring out exactly which lines of code to change and then testing! This was moved back into the synereo main repo and i then moved on to updating the local storage. This was done a month ago. The docker work got a little hung up (somebody else was doing it and now i'm taking it over).

Making the node available via AMZN AMI is actually more of a big deal than you might imagine as there are many dependencies to manage, and by making it an AMI the community is not burdened with all of that management. It also takes time to test. This goes doubly for the docker work as there are many more moving parts.

We had Justin Long take a stab at a redesign of the UI/UX. That code is here (https://github.com/synereo/nuui). The feedback was universally that that was not a good direction to go, so we backtracked to the existing UI with a gap analysis to other social media. If you have strong opinions about the UI, please consider using what we've got and giving us some detailed feedback about what you would like to see done differently.

The work with the LivelyGig team is here (https://github.com/LivelyGig/Product) and the choice to switch from Haxe to scala.js has been long anticipated. In 2012 we attempted to use an earlier version of Scala to JS, but that failed because that compiler was simply too broken to work with. So, we backtracked to Haxe and were able to make some progress (again, see https://github.com/synereo/agentui). Now that scala.js is both stable and has a good team behind it, and we have the work from the LivelyGig team to demonstrate that you can connect scala.js + react to our backend stack, we are porting the the haxe codebase to that framework while improving the UI. So, now really is the time to give us detailed feedback about the UI.

Finally, as for the PoS code, as i have mentioned in the Synereo Community Hangouts, the code began here (https://github.com/leithaus/strategies/tree/casper/src/main/scala/com/synereo) and is now here (https://github.com/synereo/agent-service-ati-ia/tree/casper/AgentServices-Store/src/main/scala/com/protegra_ati/agentservices/protocols/consensus). The documentation is here (https://github.com/leithaus/casper).

Part of the reason we hold the Synereo Community Hangouts is so that i have one place i need to communicate all these updates. It would be (and actually is) a full time job tracking down every channel and keeping every subcommunity up-to-date on what we are doing. So, while it might seem we are only talking, if one actually listens, they will see that we are making a *huge* amount of progress given our resources.

Your first 3 github links are broken

Thanks for pointing this out! This is apparently a bug in the BTT client. It includes the ';' in the URL. i edited the response above and put spaces between the URLs and the ';' and tested them. They work now. For your convenience, i have pasted them here:

Full project repo: https://github.com/synereo
Basic content delivery (CDN) mechanism: https://github.com/synereo/special-k
CDN + user model: https://github.com/synereo/agent-service-ati-ia
Http trampoline: https://github.com/synereo/gloseval
UI : https://github.com/synereo/agentui
Sandbox repo: https://github.com/leithaus/strategies
UI redesign attempt #1: https://github.com/synereo/nuui
LivelyGig: https://github.com/LivelyGig/Product
Casper initial code: https://github.com/leithaus/strategies/tree/casper/src/main/scala/com/synereo
Casper branch in CDN + user model: https://github.com/synereo/agent-service-ati-ia/tree/casper/AgentServices-Store/src/main/scala/com/protegra_ati/agentservices/protocols/consensus
Casper documentation: https://github.com/leithaus/casper

i realized that i should also point out that we issued our design goals regarding the UI redesign in this series of design docs that we published for community response:

Reactive Media Pt 1: https://drive.google.com/open?id=0B5I9qM5f_1cfdHVqT3Z1dTJNaVU
Reactive Media Pt 2: https://drive.google.com/open?id=0B5I9qM5f_1cfd1VuYWoyWlJBaE0
Reactive Media Pt 3: https://drive.google.com/open?id=0B5I9qM5f_1cfUGw3LTVjQkpsVTQ
Reactive Media Pt 4: https://drive.google.com/open?id=0B5I9qM5f_1cfQWFrUFVHbEFNUWc
Reactive Media Pt 5: https://drive.google.com/open?id=0B5I9qM5f_1cfc1BWUnVia0hRSHM

We'd love feedback right now as we are going into a coding sprint on the UI beginning Monday.

[sidhujag]

thanks will check them out

[Elokane]

We're live from Seattle on the community hangout right now. Come join us.

[fartbags]

We're live from Seattle on the community hangout right now. Come join us.

https://www.youtube.com/watch?v=gCxrwR0N-B4

[Elokane]

We're live from Seattle on the community hangout right now. Come join us.

https://www.youtube.com/watch?v=gCxrwR0N-B4

Thank you.

Here's the participant link as well:
https://plus.google.com/hangouts/_/hoaevent/AP36tYfkzAbYGmlsC1za0gR4nxzN7sUx5mMB7n4j4FPyH3liRC5gWw?eid=109002904706315055045&hl=en&authuser=0

[mightname]

Very very important!!!   MasterXchange will be closed in a few weeks.  Please withdraw your all synereoAMPs.  No exchange for synereoAMPs now!!!  Please contact poloniex to list synereoAMPs!!!

[fartbags]

Very very important!!!   MasterXchange will be closed in a few weeks.  Please withdraw your all synereoAMPs.  No exchange for synereoAMPs now!!!  Please contact poloniex to list synereoAMPs!!!

Wow... should have used counterparty XCP.

Is there any way to switch to an XCP token without master exchange stealing everyone's tokens?

[canth]

Very very important!!!   MasterXchange will be closed in a few weeks.  Please withdraw your all synereoAMPs.  No exchange for synereoAMPs now!!!  Please contact poloniex to list synereoAMPs!!!

Wow... should have used counterparty XCP.

Is there any way to switch to an XCP token without master exchange stealing everyone's tokens?

You have a month to withdraw your AMPs from masterxchange and use something like omniwallet - https://www.omniwallet.org/. While it's not great, there's no need to spend time and effort moving to CounterParty for this. Also, with Omniwallet you at least get your private keys. With MasterXChange, you were trusting the exchange with your keys.

[fartbags]

Very very important!!!   MasterXchange will be closed in a few weeks.  Please withdraw your all synereoAMPs.  No exchange for synereoAMPs now!!!  Please contact poloniex to list synereoAMPs!!!

Wow... should have used counterparty XCP.

Is there any way to switch to an XCP token without master exchange stealing everyone's tokens?

You have a month to withdraw your AMPs from masterxchange and use something like omniwallet - https://www.omniwallet.org/. While it's not great, there's no need to spend time and effort moving to CounterParty for this. Also, with Omniwallet you at least get your private keys. With MasterXChange, you were trusting the exchange with your keys.

Is masterxchange going to return the private keys for the coins to all of the owners of the coins? I wonder if they will go to jail if they don't. It seems pretty easy to email the users their private keys.

Does masterxchange have a public owner or was it run by anonymous people?

[fartbags]

Very very important!!!   MasterXchange will be closed in a few weeks.  Please withdraw your all synereoAMPs.  No exchange for synereoAMPs now!!!  Please contact poloniex to list synereoAMPs!!!

Wow... should have used counterparty XCP.

Is there any way to switch to an XCP token without master exchange stealing everyone's tokens?

You have a month to withdraw your AMPs from masterxchange and use something like omniwallet - https://www.omniwallet.org/. While it's not great, there's no need to spend time and effort moving to CounterParty for this. Also, with Omniwallet you at least get your private keys. With MasterXChange, you were trusting the exchange with your keys.

Is masterxchange going to return the private keys for the coins to all of the owners of the coins? I wonder if they will go to jail if they don't. It seems pretty easy to email the users their private keys.

Does masterxchange have a public owner or was it run by anonymous people?

This is probably a good time to buy AMP. People might want to sell for cheap instead of transfer coins somewhere else.

[kryptologist]

Hi, I had some AMP on masterxchange. What is the course of action to get my coins? Can I download a wallet? thank you