Bitcoin Forum

What is Stag?
Stag is a a new cryptocurrency in the works which utilizes the source code for NXT with a few modifications. It is intended to be as stagflationary as possible, meaning that there is little-to-no inflation or deflation of value. A usable currency needs to have stable value. People need to be confident that it will be as valuable one day as it will the next. If people expect the price to drop, they will try and get rid of it because it wont be as valuable tomorrow as it was today like fiat currencies. If they expect the value to go up, they will hoard it and it won't be used as a currency, rather, as an investment, like a stock, and the price will fluctuate wildly as people buy and sell it. With Stagflation, a currency can be a stable store of value that people have confidence in.

How can stagflation be maintained in a cryptocurrency?
Simple, currency can be introduced and taken out of a system so that there is roughly a constant ratio of people to the amount currency in circulation. So how can a cryptocurrency do that?

In Stag, for every new active account on a block, there will be 100,000 Stag introduced into the economy via a reward given to the accounts that forge the following few blocks. For every account that goes inactive on a block (this happens when an account has not been forging or made any transactions for over a month) 100,000 Stag will be taken out of the economy via a destruction of 50% of the transaction fees that go into a block reward.

The amount of Stag to be added or subtracted from the economy is called Phantom Stag. If there is a positive balance of Phantom Stag on a block, 10% of it will be given to the account that forges the block. If there is a negative balance of Phantom Stag on a block, 50% of the transaction fees will be taken from the block and destroyed, the other 50% will go to the forger of the block. The equations are as follows:

• phantomStag = 100,000 * (newlyActiveAccounts - (amountOfStagInInactiveAccounts / 100,000))
• blockRewardIfPhantomStagIsPositive = 0.1 * phantomStag + transactionFeesForBlock
• blockRewardIfPhantomStagIsNegative = 0.5 * transactionFeesForBlock

As you can see, the amount of Stag in circulation will stay relatively the same. It may fluctuate a little bit, but won't fluctuate much unless there are a large number of accounts that go inactive on a single block or a large number of accounts that go active on a single block which in unlikely.

What is to stop people with large amounts of Stag from gaming the system by creating and maintaining as many active accounts as possible?
Excellent question... The answer is Brother Trees!

As we know, new NXT accounts must use a public key for their first transaction. In Stag, the sender of that first transaction becomes linked to the new account. There will be many original Stag accounts, referred to as "Root Accounts." There will be one Brother Tree for every Root Account. Each time a Root Account sends a transaction to a brand new account (let's call it a Branch Account), that Branch Account then becomes part of that Root Account's Brother Tree. Each time that Branch Account sends a transaction to a brand new account (a new Branch Account) it becomes connected to the first Branch Account and, by proxy, the Root Account and any other accounts in that Root Account's Brother Tree.

If an account of a particular Brother Tree forges a block in which there in Stag introduced due to new branches on its' own Brother Tree, then the new funds because of accounts on that Brother Tree will be given to a random account that is at as close or closer to the root on a different Brother Tree chosen with a probability based on the number of new accounts a Brother Tree gets. This is called the Brother Award.

So, what stops people from making and maintaining a bunch of new accounts of different Brother Trees than their own? Well, if someone creates an account on a different Brother Tree, they decrease their own chance of getting a Brother Reward if they don't get the block.

Don't Brother Trees and Brother Rewards benefit Root Accounts more because they are more likely to get a Brother Reward than Branch Accounts?
Yes and no. The more and more branches there are, the less likely they are to get a Brother Reward because they have an equal chance as every account up the tree until the level of the new account. The only way they can benefit is if an account close to the Root on another Brother Tree activates a lot of accounts thus increasing their chance at getting the next Brother Reward but decreasing the chance that their tree will receive future Brother Rewards.

What stops a particular Brother Tree from becoming "better" than other Brother Trees?
Simple! The larger the Brother Tree, the more likely it is going to receive a Brother Reward but the less likely any individual in the tree is to receive the Brother Reward. For a smaller tree, the opposite is true. Therefore, there is a balance in the way Brother Trees grow and in the motivations for a individual to create an account on one Brother Tree as opposed to another.

The beauty of this system is that everyone is motivated to spark as many new accounts as possible both on their own Brother Tree and on other Brother Trees. They get a new account on their own Brother Tree and they increase their chance of getting a Brother Reward in the future but if there are too many new accounts created too fast, then that Brother Tree is the one giving the reward instead of getting it.

The Bottom Line
Steady, equal growth of each Brother Tree is combined with stagflationary economics to create an economy in which use of the currency is encouraged and the people have confidence in the currency's stable value. This currency is Stag.

Initial Distribution
The goal is to get as many Root Accounts as possible. The more people that are using Stag, the stronger Stag will be! It is for this reason that I am giving away shares in the initial distribution of Stag for free!

How much Stag will there be when Stag begins?
This number will be determined by the number of people who pre-register for Stag. The equation is thus:

amountOfStagAtInitialDistribution=100,000*numberOfPreRegisteredAccounts

The number of pre-registered accounts includes one for myself. The limit is one account per person. To enforce this, ONLY Sr. Members and Hero Members of NXT Forum and of BitcoinTalk will be allowed to claim shares!

How much Stag will I get for pre-registering?
95,000 Stag... Details below.

What percentage of the initial distribution will I get for pre-registering?
Again, this depends on how many people pre-register. I am practically broke, so I will be taking an additional 2% of the initial distribution (unless somebody talks me out of it). After all, this was my idea! An additional 3% of the share will be given away as a bounties. So, your percentage can be found via this equation:

percentageOfInitialDistribution = (95 / numberOfAccounts) + bountyPercentageReceived

Is this fair? You tell me!
Because so many people are free to pre-register (at no cost) and those who put work into the creation of this economy are the only ones given more than others (Devs, designers, exchanges, etc.), I see this as fair. If you disagree, PLEASE tell me! I want this to be as fair as possible!

Pre-Registration Details
Simply PM me here or post on the equivalent NXTForum thread (link coming soon) stating your interest! If you claim to be someone from NXT, I will double check with the NXT Forum account to make sure you haven't lied. If I catch you lying, you will be banned from the initial release, so be HONEST!

Bounties!!!
Bounties will be given out in forms of percentages of initial share distribution which will be added to the 95,000 Stag given to every pre-registered account.

What is needed!

• 1 Core Dev will be hired: +0.8%
• 1 Vector Logo. Something related to an actual stag (here is a picture if you don't know what a stag looks like http://funkman.org/animal/mammal/reddeerstag.jpg (http://funkman.org/animal/mammal/reddeerstag.jpg): +0.2% CLAIMED BY logocreator!
• Founders Faucet: a faucet website that takes funds from Root Accounts that opt in to the faucet: +0.3%
• 7 operational public Stag nodes (from different users): +0.1% each
• 1 Stag Website Dev: +0.5%
• Stag Forums Dev: +0.5%

OPEN BETA IS HERE!

Stag open beta is here! I have a public node with an open UI as well as a public node with a closed UI for it to exchange data with. So far, they have been sufficiently exchanging blocks and transactions with each-other so I am opening up the beta testing phase for public use.

What to do!
Go to the URL listed in the "Where to go" section and create an account. Write down your password somewhere or save it to your computer. There is no need to worry about security as this is only beta and upon official release, all coins from beta WILL DISAPPEAR! Once you log in for the first time, you will be given a public key. Post your public key here along with the amount of STAG you want to use for testing. I will then send you some STAG using your public key! After that, play around and goof off! If you find a bug, please post it here!

What NOT to do!
Don't use the password you used for beta for a real account when Stag is finally released as the server is set up for debugging and I WILL see the passwords you used in beta! So please, don't tempt me by using a password you used for something else or using the same password for beta as you do for the initial release!

Also, don't report typos (yet)! This includes instances where something says "NXT" instead of "STAG." I will get to these later.

What to expect!
Likely the biggest existing bug is the fact that when you try to make a transaction, you will see an error stating "Could not verify signature (Server Side)." Despite the error, the transaction IS excepted and will go through in the next block. This has something to do with the fact that you are logging in remotely (i.e. you are logging into Stag through something other than localhost). I am aware of this bug and will fix it, but it is not my highest priority as every day use of Stag will be done through localhost.

Another major bug is that forging crashes after 31 blocks due to too many data base connections. Until then, I will periodically reset Stag and will send out transactions to beta testers who have given me their information every reset.

Where to go!
To help with Beta Testing, go here: http://104.131.29.158:7826 (http://104.131.29.158:7826)

Known Bugs

• "Could not verify signature (Server Side)"
• Number of confirmations don't update in on Dashboard
• "No blocks found" on Block page.
• Forging crashes after 31 blocks.

Stag and Anonymity
I would like users of Stag to have as much privacy and freedom as possible. It is for that reason I have taken a break from development to investigate internet privacy techniques. After some thought, I have come up with some ways of increasing privacy for Stag users.

Key Pair Shifting
This is something of my own design. I figured it would be much harder to track a user if their public and private keys change on a regular basis. So I came up with a design for doing just that.

The Stag wallet file will contain a set of private keys rather than just one. Each user will be allowed as many addresses as they want. They must, however, be aware that this takes up space on their computer's hardrive. These addresses are disposable much like Bitcoin addresses.

A transaction, rather then being made by sending coins from one account to another, is made by adding a 2 dimensional array to the address in question which contains a set of address and amount pairs. So the contents of that address are transferred to other addresses. In this way, an address almost works like a transaction. Once it is declared where the coins are going, the address becomes locked and no further changes to it can be made. It is because of this, the full amount of Stag associated with the address MUST be transfered to somewhere.

Now let's say someone's address contains 10 Stag and they only want to send 5 Stag to someone. The program will generate a public/private key pair (which means a new address) for the user. When the contents of the old Address are transfered, funds will be split between the address they are sending funds to and the new address they generated.

To prevent overlap of addresses and key pairs and to simplify the sending process, addresses will be assigned categories. The first category is the "Open Address" an Open Address can hold as much funds as it wants. There is no limit to how much it can hold. The remaining catgories are called "Locked" or "Fixed" Addresses. They can only contain one set amount or nothing at all. They will be split in binary fashion. There will be 1's Addresses, 2's addresses, 4's addresses, 8's addresses and so on and so forth. This limits the number of fixed addresses a person needs. Either they need 1 of a particular category or they don't need that category at all.

Another benefit of this is that it makes Stag divisible an infinate number of times because each address contains only a true false value (full or empty). It also allows for a near-infinate number of Stag to exist as it is not limited to the max size of a Big Integer or a Long but rather by 2 to the power of the max size of a BigInteger or a Long.

ZenSage's i2p + Tor + Encryption Server Integration
I have been in contact with someone I only know as ZenSage. I met him through a NXT user. ZenSage is working on an advanced anonymity preservation method for browsing the net. Here is the basics of how it works:

The user requests a website. Their machine first sends out a request to a Database Server Eepsite through i2p and tells it the website the user wants, what encryption algorithm is to be used, and a unique request identifier. The website data and the encryption algorithm are both encrypted so that only a particular Encryption Server can decrypt them. This way the Database Server Eepsite doesn't even know what was requested. The request is sent through a pseudo unidirectional connection so the server doesn't even know who made the request.

Next, the user's machine builds a Tor cell with a randomly chosen Tor path. It sends this Tor cell and the first Tor node in the path through i2p to a specialized outproxy. A Tor cell is wrapped in layers of encryption so the outproxy doesn't know anything that could identify the requested website. The outproxy forwards this cell to the first node on the chosen path.

That node decrypts one layer which reveals the next node. The next node decrypts a layer which reveals the node after that, and so on until the cell reaches the exit node which decrypts the final layer that reveals the a web address and the IP of the outproxy.

The web address that the final node receives, rather than containing the website that the user requested, gets a web address to an Encryption Server containing an encrypted version of the unique request identifier. The exit node then opens up a stream to this web address.

The encryption server then makes a request through i2p to the Database Server Eepsite asking for the Unique Request Identifier it recieved from the Tor Exit Node. The Database Server Eepsite sends the requested url and encryption algorithm (which are encrypted) to the Encryption Server which decrypts the requests.

The Encryption Server then optionally opens a stream to the URL through i2p and Tor if they want to avoid harassment due to the potentially unsavory nature of the url's it retrieves for the user. Otherwise, it opens the stream directly to the URL (which would be faster).

The Encryption Server takes the data packets it receives from the URL as they come in and encrypts them so that only the user can decrypt them.  It then returns this encrypted stream to the Tor Exit Node.

The Tor Exit Node receives the encrypted data stream and forwards it to the Outproxy. The Outproxy forwards the encrypted stream through i2p to the user's machine. The user's machine decrypts the stream and feeds it to the user.

Who Knows What In This System?

• The user and their machine almost everything. Enough to compromise the user if their machine is hacked.
• The Encryption Server only knows the Unique Request Identifier. The URL and encryption algorithm the user requested are encrypted to they can't read the data.
• The Outproxy only knows something (ip address or i2p identifier?) which tells it how to send the data back to the user. If this is compromised, the User is possibly identified but what web address and what contents are still unknown. The user is still safe.
• The Tor Exit Node only knows the the IP address of the outproxy and the IP address of the Encryption Server. If it is compromised, a spy might know where to start looking for data on the user. This only lasts as long as the user is accessing the website, however; so, it would be very hard to identify the user with this as a starting point.
• The Encryption Server knows the IP Address of the Tor Exit Node, what url is being accessed, what exactly the url contains, and the Unique Request Identifier. If this is compromised, a spy would have potentially dangerous information about what the user is doing and have a starting point for where to look to find who the user is. However, like the Tor Exit Node, the ability to track the user only lasts as long as the user is connected.

Because of all this, it is safe to say that a potential spy would need to compromise the Encryption Server, the Tor Exit Node, the Outproxy, and anything inbetween the final connection the user has to the Outproxy (if there are indeed inbetweens) all within the time frame the user is connected. Add to this the fact that there are over 1000 possible Tor Exit Nodes currently in existence and that there may, potentially, be multiple encryption servers that the user could connect to. In short, things look pretty bad for a spy trying to get information on a user.

Why Integrate Stag With This System?
The main reason is because with NXT, it is very possible for someone to identify the IP address of a particular account by collecting a large database of public nodes. From there, someone could identify what IP address is connected to what set of nodes. If they listen to all the public nodes, they can gather the NXT address associated with that IP address by determining which set of nodes they recieve the transaction from first. Doing this multiple times could result in the determination of the exact IP address a particular account is being accessed from.

Simply adding Tor to that doesn't help much either because someone could determine the source could still be bad because someone could monitor whenever a Tor Exit Node connects to a NXT public node and trace the connection back to the user's IP address.

Just i2p integration with Stag is better than just Tor but still not very good because within i2p, it is possible to identify which lease set is associated with a particular Stag account. i2p has yet to recieve much peer review and it may be possible to identify the IP of someone through their lease set.

Using the method described above, no one who knows anything that could possibly identfy the user can even know that the user is running Stag let alone associate their IP address with a particular Stag account/ID.

So you're launching a coin without everything in the above list?

Good luck.

ONLY Sr. Members and Hero Members?

:(The level is too high。。。

 your NXT Forum username and your BitcoinTalk username  :o

 its the ad for  NXT Forum ?  :-\

I don't have NXT forum id...

Good luck.

Fierce

Sr Member and Free, those words make me say why the hell not !  ;D

Sr member and hero membr ?
so you, NEWBIE dev you can't get free share

The old man game ;D

nxt forum? why is that essential?

I've been around a while, I just wish to remain anonoymous, and because I am not asking for people's money, I feel no need to prove my own seniority.


Well, the original reason was to help keep people from gaming and doubling their Stag by using two accounts but I suppose it is still possible (although more difficult).

 Because so many people on BTT seem not to have an account on the NXT Forums, I will not require them to sign up for it. (Only those from the NXT forums will be required to provide both accounts.) Updating the OP.

thanks, will follow this one.

like o get involve. ;D

i like also to get involved

I have one acccount.

Is the core dev to add these changes to the NXT code base or is Stag ready to-go?

I would like to be involved on this project.

I don't have a ID on the NXT forum.


Ps. I'm not sure if this way is the best one for the distribution, maybe would be better through PM. Moderators don't like that people ask for their shares on the forum.

I want to be in!
It looks to be a nice project

Count me in! :)

You most likely only have one account. The only problem is that I cannot confirm this. If I require a minimum level of Sr. Member, the probability that someone has more than one Sr. Member account is very unlikely. That is why I am requiring a Sr. Account. Further, I am pretty far away from launch (depends on how quickly people claim the bounties). You are a Full Member, yes? That being said, it is very likely that before the launch of Stag, you will be a Sr. Member. :) Even if you don't, you can get in on Stag by claiming a bounty in which case I will make an exception for you. ;D


THANK YOU SO MUCH! These are awesome! You definitely get the 0.2% bounty even if you aren't a Sr. Member! Please send me the SVG in a PM. ;D Updating the OP with it now!


It needs some work. I will be working on the code along with the core dev. I just don't have the time on hand to do it all by myself and get it done quickly.

+1, I don't use NXT but this time i wanna try. :D

Thanks. :)

THANK YOU ALL FOR YOUR SUPPORT! At the time of my writing this, here is how many Brother Trees it looks like we will be having:

From NXT Forum (Unconfirmed): 42
From BitcoinTalk: 10
Total Interest: 52 Users
Total STAG at initial release so far: 5,200,000

Here is an Idea for the logo
https://i.imgur.com/Q7KcROK.png

I am interested. Hopefully I will become Hero Member before this closes.  :)

Nxtforum - logocreator (https://nxtforum.org/index.php?action=profile;area=summary;u=3273)
BitcoinTalk - logocreator (https://bitcointalk.org/index.php?action=profile;u=370533;sa=summary)

so..i think i'm qualified right?

Definitely!

You need 240 activity to become a senior member.  You get like 7 activity per week, so I'm still a good 4 weeks off from qualifying.

STAG will likely be in a testing phase by that point so chances are that you will qualify before Stag's official release.

In that case... Count Me In!!

+1

I am near to be a senior member (2 points away). So i think i will be qualified at starting time.  :D

Oh, I am sure!

I just got word that Bitscoinshop.com.br will be accepting STAG upon its release!

Please also note that I still need a core dev to work with. I can do Java, but I am a busy man and don't have as much time as I would like to commit to its development. There is a bounty for someone who works as a core dev!

Think I'll go ahead and say "I'm in!".  ;)

Although I am in because I am a SR. Member and there is Free coins, This Merchant is just plain rubbish, they de-list accepted coins without informing the Coin Dev/Marketeer & only list for Bribes/Unreasonable Bounties, I've dealt with them personally before in saying this !

P.S I don't think anyone has even bought anything from them lol

let me in please,
one share reserved. lol

thanks

I am interested. YAY STEAK TYME!!! Lol, got it in my fav bar. Don't let us down ;)

So.here i.sit with a rather ~300ish post count and with no chance to.get in. This is messed up. I bet the next coin announced this way will.be only.for legendary members "just to.make.sure people.don't get double stakes ane dump them instantly"
And launching without a core dev is a MAJOR issue. It's like saying hey guys i got this cool idea but i don't know how to even.start doing it but to join me you have to have this special status. Bah.

damn.im so close to sr ::)

Stating my interest and watching thread.

Yes, me too. But we will reach the "senior" until the official launch.

my nxt id is not sr above...

I'd consider "Full Members" - the Middle Class of CryptoLand....

And either/or it on BCT & NXT Forums....

Cool Logo....

QQ.why.do.you keep talking.like.this.?.

Because of the "fair" intent of the developer. A lot of people is being excluded from the "fair" distribution.
The previous one was my first post at this thread

but you know: his coin - his rules.  :-\

my BTT account is Sr , but NXT forum level is newbie .
let me in please.


thanks

Thank you Doug!

im interested hope you let me in.

It doesn't matter! You are a Sr. here!


Ok, I think I have a better idea. Only accounts created before I posted the announcement are allowed to be part of the distribution. This way people of all levels of seniority can join. Do you think that would be more fair?


Thank you for telling me! I will ask around and see what people's experience with this merchant is!


PLEASE NOTE: There is already one core dev... ME! I just need another because of the limited amount of time on my hands.

Also note: This has nothing to do with dumping instantly. Just the idea of people doubling up. I am open to considering allowing more people to join and I think I have an idea on how to do it while making it hard to double up. I will announce when I have come to a decision.

Nice Idea! Count me in please!

That is some what good idea, but i know atleast one guy (can't remember his nick tho) who has 100+ accounts here.. atleast that was back in May.

Altho i do not have any better idea.

Maybe if you take "member" and above.. i don't know. it's your call.

Good luck.

I hope i'm in.

Hello,

I would like to be involved in this project.

Thanks

Yeah - I think most of us have seen the result when there are no stipulations on free distribution - mass n00b registrations and multiple accounts leading to one heck of a lot of work if you're going to try to keep it fair. Trying to weed out multiples requires a lot of work for one person.

Therefor, I think it's best to at least stay above "Member" status. But - that's just me.

I have an account NXTforum in a long time, but have not done enough posts to get more than one star.
Note that this forum is not as active as this one.

I propose that you make a list of stakeholders from other lists, such as those made ​​for distribution of other coins, or owners of other existing ones.
Could get a list of NEM for example, they are being quite fair distribution.

You only have to be a Sr. Member in one of the forums. So, you're in.

count me in.

Interested

interested, i'm in.

looking forward . count me in

I would like to be included in this distribution, but I thought I better warn you that giveaway threads are not allowed here. There is a whole thread (linked to below) stickied at the top of the alt section explaining this

https://bitcointalk.org/index.php?topic=434310.0

It says

Most giveaway threads are no longer allowed in the Alternate cryptocurrencies sections. From now on, posting or replying to such threads could result in being banned. Existing threads will be locked.

Specifically, you are not allowed to give people any incentive to post insubstantial posts in your threads.

I have seen numerous threads like this locked because of page after page of posts saying nothing more than "interested". The OP is often banned too.

An acceptable way of doing a giveaway is to ask people to pm you to let you know they are interested. The mods here are OK with that.

good coin,,, join in this coin .thankd dev

Count me in, interested!

good coin,,, join in this coin .thankd dev

I would like to get in on this coin...I am not a senior member, but have contributed to both the BurstCoin thread (via a guide writeup) and I have an NXTforum.org account as well: mi9ner. I have a marketplace account on the NXT market also. Hopefully that would be enough to prove that I am who I say I am, and that this would be my only account. Let me know, Thanks!

Will do. I will update this tomorrow night. Thank you for the information.

I want to join, but I am not sr members.
I have a NXT account for a long time, there are many deals. The address is  NXT-MQQN-U2TF-DKMK-29HT4

you cant add full members?

I updated the op so as to ask for PMs here on BTT rather than "interested" posts. All posts (not including the ones already made) simply stating interest on this thread will be ignored.

1. XCASH is right.  It better be made clear that PM is the only way to go.  (basically say on the front page, "DO NOT ASK TO BE IN STAG IN THE THREAD")

2. This looks like an interesting project.  I will be putting it in my favorites and I will send you a PM  :)

If he adds full members, then a ton of sock puppets can come in.  Around the time full member accounts were created there was a flurry of accounts being created here from people trying to get extra shares in coins just like this one.  So, I can understand why he says that full members can't come.  

That said, I think there should be an exception.  I'd say it is more than fair to allow full members with more than 480 posts (future hero member) to be a part of stag. Also, the account can't have a negative trust (some sock puppets were also prolific trolls). This ensures they are not definitely sock puppets and real members of this forum.  

Agreed with you, the op reasons are understandable, and your idea of exception seems quite fair, +1

Unfortunately I'm no Sr. member or near it, but I liked the coin and hope it does well.

Details are avalible here: https://bitcointalk.org/index.php?topic=823638.0 (https://bitcointalk.org/index.php?topic=823638.0)

Hello.

Is there list of stakeholder already available where we could check
if we were added to the list and how many people (accounts) requested to join?

Thanks.

I would also like to know.

Will work on it today. Thank you for your interest.

Note, there are a few spots which say "RESERVED." Those are for my family members (or in one case, my dev) who do not yet have accounts on either NXTForum or BTT. I have not added members of NXTForum to this list yet. A lot of them are NXT newbies but claim to be Sr. or Hero Members here on BTT and I need to verify their BTT accounts. This is a daunting task. Thank you for your understanding!

I'm twice  on the list, please fix this, it was my fault because I've PM'ed you after OP update

Please Count Me In!
With a fair distribution of this coin here will be a big success.

I'm twice in the list, please fix this. I have written in the thread (but was not a seniormember then) and sent a pm as seniormember days later. Thanks

Nice project and I hope I'm not late for the party.
Looking forward to your progress.

Not at all too late, send me a PM.

Gonna HODL  ;)

i sent you a pm, count me in.

can i join it?

When are you gonna launch ?

please ,consider increasing the free distribution

have sent a pm, count me in.

I don't want to make any promises but I have made significant progress on the code. I am already starting to test it privately. Soon I will start to test it with the second dev I have signed on. It will likely launch before the end of the year.

I would also like everyone to note that Stag will implement transparent forging. For those of you who don't know what that is, it means instant transactions while maintaining blockchain security.

I hope you can get some more members.  I like getting more for me, but I am one of those people that believe a wider distribution is a lot better.  I would rather not see another distribution with 72 people. 

Otherwise, I still think your idea is really cool.  In someways it is like lots of little sidechain blockchains all being put together to make one big blockchain.  Very neat.

As you see in my signature, I'm very interested in "stable-price" coins. So I would like to join this experiment. I've posted in Nxt forum too.

Don't worry, there are a lot more people interested on NXTForums.

just sr member ,
it will be a deadcoin.

yes, why sr member?

Because they are more trusted as their accounts & name are alone worth more than 1 BTC "Usually"

Only Sr. Member and up for initial distribution. After the release, anyone can get it.



Trust me, I have. I considered it and thought it wise to only include Sr. Members and up in the initial distribution with the exception of immediate family and members who claim bounties.

That being said, there is no need to worry! I will be giving away a lot upon the release. I am aware that giveaways are not permitted on BTT so I will run it on NXTForums. On top of that, I will run a faucet. Granted, it is unlikely that you will recieve 95,000 STAG for it, but you can still get some before it hits an exchange and becomes worth something. I will keep everyone posted!

full member is great.

Still not like SR.member... I will wait for initial offer to pass, will watch this.

we are late then?  :o

Best Wishes on my point.

One of the different approach to a coin.

Glad to be here.

ok. let's buy sr member accounts  ;D

Hmmm... Thinking of selling mine at the bargain-basement price of just 10BTC  :D

Hello.

Have sent a pm, count me in if you can please.

thx

lol, now sr member not trusted anymore  ;D

You guys can buy my account for 5btc  ;D

Easy guys, you can get banned for this kind of posts...

Not that I am encouraging account buying/selling, but I am flattered that people would be willing to buy accounts just to get a stake in a coin that hasn't been released yet. ;D

Yeah. maybe this is worth it. i'm glad my name is on that lisr. :D

Hi, man, I just kidding  :D Of course I won't sell my account.

Yeah - I was only kidding as well.

I know you two are joking, but maybe mod wont be in a mood for it... :) You see what i did there?  ::)

Anyway, will be participating as first distribution stage is done.

So perhaps a mod would need a mood mode modifier...  ;D (I definitely didn't get enough sleep last night  ;D)

Looking forward to this!

interested

That just made my morning. "Mood mode modifier" lol!


Then send me a pm. Can't do giveaways on the threads.

Soon I will be releasing a password/account/public key/genesis transaction generator for people to use. It will be password protected and I will send out the passwords to individuals who are preregistered. I ask that people who have claimed bounties be patient as I need to do all of you last because you are getting a certain percentage of the total.

I will be using java to sort out members so I don't accidentally get anyone twice.

Once I start recieving the information I will make a list of accounts numbers, transaction signatures, and public keys sorted by account number numerically. This way your Stag account can remain your secret if you wish don't wish it linked to your BTT or NXTForum accounts.

You will be responsible for writing down your information and double checking to make sure I got it. If you lose your password, tell me and we can work something out as long as you can prove that you own the Stag account ID in question.

plz reserve for me

gonna look forward for Stag!  ;D
PM sent dev  ;)

This coin may be worth 5btc, community coin was worth 1-2 btc per person.   ;D

Stag is better than COMM.

just sent pm... ;)

Sounds very solid surely will catch eyes of investors.
PM Sent.

Hope for the better >>>
PM sent ..good luck

just sent pm,
hope for big future...

Good luck with Stag.

How long till the end of first round of distribution so that others then sr. and etc..., can join?

It will be until Stag's official release which I can't say when that will be exactly. I have run into a weird bug because I changed the contents of the HTML file so that it says STAG instead of NXT everywhere and now when I try to do a transaction it says: "Fee not specified."

I have asked for help from some of the NXT devs but so far no one has answered. On a related note:

The beta version of stag has been delayed. I still hope to get it out soon but I have run into a bug that is slowing me down.

I have asked the NXT community for help but have not got an answer yet. Rather than be unproductive and simply wait for the NXT community to respond, I have decided to work on an add on for NXT that will also be implemented in Stag.

This add on will open up legacy JSON-RPC commands used in Bitcoind for use by developers. This will make it easy for exchanges and payment processors to accept both NXT and Stag. Rather than having to learn new commands and write new code for NXT and Stag, they will be able to use the Bitcoind commands they are used to and have already written code for.

In addition, full JSON-RPC 2.0 will be supported with named parameters and new, NXT/Stag-specific commands will be added, providing a rich JSON-RPC 2.0 development environment for developers to utilize if they prefer it to the standard NXT and Stag protocols.

Like the standard NXT API server, the RPC server for Stag and NXT will support https connections, and like Bitcoind, it will support RPC username/password protection. The https connections allow for safer transition between the server and the client and the username/password protection protects the server from unwanted access to commands.

The RPC server can be configured for multiple usernames and passwords and assignment of privlege levels to each is supported. Optionally, certain commands can be permitted for use by unauthenticated users on the server. For example, transactions cannot be sent by unauthenticated users, standard users can access information about their accounts and send transactions in their accounts, admins have access to everything.

This user permission level system will be ideal for exchanges who wish to keep each user's balance in user specific accounts rather than a centralized account.

Hopefully I will hear back from the NXT community before this project is finished, otherwise I will have to find the bug the hard way. :(

Any progress in your project? Did you get response from the NXT community?

No response yet. I am going to take it to the other Stag dev to check out sometime this week. In the mean time, I am going to continue developing the RPC interface.

Edit: I found the problem and have been able to progress with debugging! :) The error was a single extra whitespace in the code. No wonder it took me so long to find it!

Good news, good work.  :)

registration still ongoing?

I think yes but you need to send him a PM.

And you need 2 activitypoints more to reach a "seniormember".

Debugging has been MUCH smoother since I got rid of that one bug! I fixed 5 bugs in the forging code just this morning! (I have only been awake for about 2 hours).

Hopefully nothing that tricky comes up again so I can get Stag 0.0.1 out sooner rather than later.

Stag 0.0.1 most likely won't have all the additional security features (such as the pseudowallet file and second public key) enabled but will have some of them fully implemented (such as the enhanced password generator).

In case you don't know, the pseudowallet is like having a second public/private key pair, except, rather then being generated via a password, the private key is generated directly through a random byte array and is capable of providing higher entropy because it is not dependent on a password (providing better security). In addition, the public key is also capable of being much larger, making it more difficult to brute force the private key which corresponds to the public key. The pseudowallet file contains a reference to the transaction that contains its public key so it is quickly found.

To provide extra security, the pseudowallet file is encrypted using the standard Stag password. This forces potential attackers to find the password before they can find the second private key. Because the wallet file in encrypted with a different algorithm than is used to generate the standard private key, the attacker would need the exact password used to create the account rather than just finding the account's private key and using it to unlock both the standard login and the pseudowallet file.

So basically, with the pseudowallet file, an attacker would to do one of the following:

• Brute force both the standard private key (which is already difficult) and larger, more difficult, pseudowallet private key.
• Brute force both the account's password and the pseudowallet private key.
• Brute force the account's password and steal the pseudowallet file.
• Steal the account's password and steal the pseudowallet file.
• Steal the account's password and brute force the the pseudowallet private key.

In other words, it would be quite difficult to hack someone' account if they have a pseudowallet implemented.

The enhanced password generator, which will be implemented in Stag 0.0.1, is also really cool. First of all, it implements a larger array on English words than the NXT password generator, providing better entropy. It optionally, implements the HotBits true random number generator on top of a pseudorandom number generator (the pseudorandom number is meant to provide security in case HotBits becomes insecure for whatever reason e.g. they are hacked, the connection is intercepted, something goes wrong with their generator, etc.) which provides higher password entropy. It will support multiple password sizes (so no one can just find the password and know what it belongs to based on number of words or characters). It will support multiple password languages for easier commitment to memory for speakers of languages other than English, and it will, optionally, allow creation of passwords using random characters rather than words for the extra paranoid who wish to save passwords in something like KeePass.

In other words, it will provide better security than the NXT password generator by adding new features, both for the standard user and the paranoid user, and it will be more user friendly by allowing passwords to be generated in the user's native language.

Like I said, the enhanced password generator will be avalible in Stag 0.0.1.

Expect Stag 0.0.1 to be released sometime around New Years (may be sooner, may be later; I want to make sure it is as secure as possible before it's release; I don't want anyone to lose any money).

Thanks.

So, development is going well. Stag is actually mostly functional already. Having a little trouble with the asset exchange functionality which might spill over into the DGS, but other than that, it works great!

Nice to hear. Thanks for update.

Great, we are still watching this, looks promising.

I figured out want is going on with the AE bug but I can't find what is causing the problem in the code. I have also gathered that the bug is not due to my modifications to the code but is actually present in the unmodified NXT code itself. In short, what is happening is that a certain part of the JS code is not being executed at all and leaving a variable unassigned. This problem is specifically related to issuing assets on the AE. I will try to fix it, but I have also pointed the issue out to NXT devs as it affects NXT as well as Stag.

Great, thanks for update.

According to one of the main NXT devs, asset issuance has not been having any problems. I cannot find any explicit references to the function that is not executing in any of the JS code so I will check the HTML code for explicit references and then look for implicit references in the JS code to try and figure out why this function is never being used.

No stag for me  >:(

Sure, you can get stag! I will be giving some away after release. :) Just can't be part of the initial distribution.

I fixed the asset exchange bug and am now testing for more bugs. That being said, I haven't found a new one yet. So things are going well! Will be opening up for testing soon.

Nice progress!

good to see that now we are entering to an exciting phase :) :)

Great work Stag :)

Watching

Got some interesting new bugs showing up. Open Beta may not be released as soon as I had hoped. On the bright side, I get to have more fun debugging!

It's great that you slay them bugs BEFORE launch. we've seen so many f'd up launches when there was not proper testing..

OPEN BETA IS HERE!

Stag open beta is here! I have a public node with an open UI as well as a public node with a closed UI for it to exchange data with. So far, they have been sufficiently exchanging blocks and transactions with each-other so I am opening up the beta testing phase for public use.

What to do!
Go to the URL listed in the "Where to go" section and create an account. Write down your password somewhere or save it to your computer. There is no need to worry about security as this is only beta and upon official release, all coins from beta WILL DISAPPEAR! Once you log in for the first time, you will be given a public key. Post your public key here along with the amount of STAG you want to use for testing. I will then send you some STAG using your public key! After that, play around and goof off! If you find a bug, please post it here!

What NOT to do!
Don't use the password you used for beta for a real account when Stag is finally released as the server is set up for debugging and I WILL see the passwords you used in beta! So please, don't tempt me by using a password you used for something else or using the same password for beta as you do for the initial release!

Also, don't report typos (yet)! This includes instances where something says "NXT" instead of "STAG." I will get to these later.

What to expect!
Likely the biggest existing bug is the fact that when you try to make a transaction, you will see an error stating "Could not verify signature (Server Side)." Despite the error, the transaction IS excepted and will go through in the next block. This has something to do with the fact that you are logging in remotely (i.e. you are logging into Stag through something other than localhost). I am aware of this bug and will fix it, but it is not my highest priority as every day use of Stag will be done through localhost.

Where to go!
To help with Beta Testing, go here: http://104.131.29.158:7826 (http://104.131.29.158:7826)

STAG-K8VN-HW5A-6DWK-23Y9Z
e96db5285ed13f5bc6ceaf8ccad9d578065fc7910a5debcbd4b4bf9efb61be2f
5000

Welcome to your new NXT account. Your account ID is STAG-S7JW-3ZS4-MA3V-BRL28 - When funding your account for the first time, you also need to include your public key, which is 9ba8e59a8f242e7c293485247a4183b65152b06df68ad43f8503afd304a97757

any ammount will be fine for testing  ;)

Interesting update..

Note we shouldn't be posting addresses in the thread itself or it might get locked.  Have to put it in your signature.

Nice job. i will send my my key and desired amount as an pm.

Hello stag.
Any amount will be fine for testing


Welcome to your new NXT account.
Your account ID is STAG-9EEN-HNVB-CLEB-D7DAP - When funding your account for the first time, you also need to include your public key, which is 8cc19fff333ce9fecec455df0dd6e48e4101f10d9cec084666b59e8644680541

Good work, sent my accountnumber and publickey in pm, thanks.

It is worth to observe this project

I found a bug which causes Stag to crash once 31 blocks have been forged. Until this is fixed, Stag will be periodically reset and funds will be resent to testers.

This bug has something to do with too many database connections being opened (I think). I am taking today off but will do my best to fix it as quickly as possible.

Thank you all for your understanding and support.

Good point. Or put it in a pm.

congrats on getting a Beta up.  I logged in and it looks good. Well... it looks just like NXT, but anyway, it is nice to see some progress coming along.

But beta is down. :(
http://104.131.29.158:7826/
This webpage is not available
Google Chrome's connection attempt to 104.131.29.158 was rejected. The website may be down.

You just have bad timing. I was just doing a quick update which hopefully fixes the 31 block bug.

Why are you forking with a dead coin ?

Sorry, I forgot to change a setting in the config file. It should be working now and all coins should be sent out.

It works for me. Testcoins received. My Stagaccount is in my sig. If someone send me Coins i send it back. Please put your accountid in your sig.

ok i received some coins i return to you 500 but i have this message : Incorrect transaction: nxt.NxtException$NotValidException: Double spending transaction

How do I get a stake, or is the distribution over? I think there is a market for a good NXT alternative. QORA flopped, and currently NHZ seems to be doing decently. You need to promote it well - twitter, facebook, maybe hire professionals like gloryninja's (https://bitcointalk.org/index.php?topic=650780) service.

I cant send Coins. "Incorrect request".

edit: I got the testcoins but there is no confirmation (0).

edit 2: confirmation received and coins sent. Get the message above, but coins are sended.

Just send me a PM saying you are interested in initial distribution. :)


Odd, I received the coins back. Thank you for finding the first bug (well the first one I haven't found yet).

i test again with 25 stag i think you received but it's in red here.



http://img15.hostingpics.net/pics/461636stag.jpg (http://www.hostingpics.net/viewer.php?id=461636stag.jpg)

can i have some Stag for testing?

OPEN BETA IS HERE!

Stag open beta is here! I have a public node with an open UI as well as a public node with a closed UI for it to exchange data with. So far, they have been sufficiently exchanging blocks and transactions with each-other so I am opening up the beta testing phase for public use.

What to do!
Go to the URL listed in the "Where to go" section and create an account. Write down your password somewhere or save it to your computer. There is no need to worry about security as this is only beta and upon official release, all coins from beta WILL DISAPPEAR! Once you log in for the first time, you will be given a public key. Post your public key here along with the amount of STAG you want to use for testing. I will then send you some STAG using your public key! After that, play around and goof off! If you find a bug, please post it here!

What NOT to do!
Don't use the password you used for beta for a real account when Stag is finally released as the server is set up for debugging and I WILL see the passwords you used in beta! So please, don't tempt me by using a password you used for something else or using the same password for beta as you do for the initial release!

Also, don't report typos (yet)! This includes instances where something says "NXT" instead of "STAG." I will get to these later.

What to expect!
Likely the biggest existing bug is the fact that when you try to make a transaction, you will see an error stating "Could not verify signature (Server Side)." Despite the error, the transaction IS excepted and will go through in the next block. This has something to do with the fact that you are logging in remotely (i.e. you are logging into Stag through something other than localhost). I am aware of this bug and will fix it, but it is not my highest priority as every day use of Stag will be done through localhost.

Where to go!
To help with Beta Testing, go here: http://104.131.29.158:7826

@atchoum6760 i created Stag account, i just need some Beta Stag to test  :P.
I am getting this error
Warning: You are most likely on a fork (you have forged the last 10 blocks).

It is supposed to be in red on yours because that is STAG taken away from your account. It is green on mine because it is STAG added to my account. It doesn't mean there was an error.


That is normal when there are less than 10 blocks and we ARE technically on a fork of NXT; it is just a fork at block height zero.

If you want some to play around with, send me a PM with your account and your public key.

There was a crash on the node I linked you guys, too due to an error in the code which finds the Brother Reward recipient for the block. I will be updating it momentarily. I will try to save the DB but I might have to get rid of it which would mean sending all the test transactions over again which might take about 30 minutes. Thank you all for your patience!

---

I have reset the server with an update. It should now be able to function for a large number of blocks without crashing. I have also sent out test Stag for everyone to play with again.

I issued a test asset as well. I would like all beta testers to buy and sell some of it with their test coins to make sure the Asset Exchange functions properly. It will go through at block 2. When it does, will post the Asset Id and Issuer Id below so you can find it. Feel free to issue new assets to test as well.

Asset ID: 5483821208322915655
Issuer Id: STAG-K96U-N3NP-4ZWG-4R7YT

This is appreciable that things are moving in right direction. keep up great work.

Building a crypto (even a fork of an existing crypto) is not easy if you you are going to do it right. I basically work full time on it because it is very important to me that I do this right.

added a buy order for the asset.  :D

added a buy order and a sell order. :) Seems like it is working so far.

For buyng i have this message : Could not verify signature (server side).

That is a known issue with the public UI. The transaction does go through though. It will happen with every transaction you make.

oki i see my orders !

Buy Orders (3)
Account   Quantity   Price   Total
STAG-EA2P-84PJ-PUWB-GC6DU   500   0.1   50
You   500   0.1   50
You   500   0.1   50

Buying and selling asset without any problem (known issue message). But i can't send stag. Incorrect request.

message answered (Incorrect transaction: nxt.NxtException$NotValidException: Double spending transaction) but sent.

1. Its only possible to send next to your (Stag) account. By all other recipients i got the message: incorrect request.

2. Buying and selling assets is working but can't see my  "open orders".

1. I noticed this too. It happens after you send your first transaction per log in. You can get around it by refreshing the page and logging in again. I will work on fixing this as one of my top priorities.

2. Same type of thing as above. If you refresh and log in again, it fixes the issue.

Made transaction and buying&selling of asset is also working.

Edit: getting this error while making a transaction "Incorrect transaction: nxt.NxtException$NotValidException: Double spending transaction"

Will be dumping a bunch of test Stag into an inactive account. This should cause Brother Rewards to be sent out (as Stag will enter a phase with new Stag being added to the system). I want to make sure other accounts are getting added to Brother Trees properly. If you recieve a BR, please tell me so I know it is working. You will know you have received one when your balance suddenly goes up but nothing is added to your Forged Balance. Thank you to all my testers!

Pm sent, interested in initial distribution.

Thanks.

For me all it's good.Sent and receive ok.

Me too. Tested sending and receiving coins, also assetbuying and sending messages. Except the known error messages everything is working normally.

Received the following error when trying to send some out of the "test" account STAG-E8JD-FHKJ-CQ9H-5KGMQ to my test account STAG-3GLB-9UWX-ZP8F-FS6R2, transaction hash: 3b60ba0fd104d58ddede397c415fc1d63bb2d67882513d27f5d39ffe38642b23


However, coins have apparently been received ok. Seeing same error when sending coins back as well.


ps: If you want me to maintain a testing node, please send download url or PM. (or maybe wait until database crashing bug is resolved). Cheers!

same error above, but sending and receiving coins ok.

same here.

This makes me uncomfortable considering the transactions are going through. If a double spending issue comes up, the transaction should NOT go through. Could someone please try sending more coins than they have back to me to see if the transaction still goes through?

And someone else try sending all their coins to another account and then try sending more in a separate transaction on the same block. I want to make sure REAL double spending transactions don't go through.

EDIT: I forgot to activate the account on the second brother tree so it has just been collecting inflationary block rewards with no brother rewards going to other accounts because its Brother Tree was completely inactive. I fixed it now so people should start receiving Brother Rewards. About 10 of them will happen before we even out the total Stag in the economy and the ideal stag in the economy.

I would but I don't want to distribute demo versions of Stag to people I don't know just in case someone trys to distribute it before it is ready.

EDIT: Happy Thanks Giving to all my US friends!

me too..

Most of the time I do not get any error but I received again, the "Incorrect transaction: nxt.NxtException$NotValidException: Double spending transaction" but after that transaction went successfully, it would not let me "double spend" in the same block, telling me "Not Enough Funds" as it should. I did not try using the API at http://104.131.29.158:7826/test only the GUI. I'm sending between accounts STAG-3GLB-9UWX-ZP8F-FS6R2 and STAG-E8JD-FHKJ-CQ9H-5KGMQ

Thanks for your help. If you can try it with the api, I would appreciate it a TON.

I have made progress getting the blocks visible. I even made a little page search box so you can browse every block from the comfort of your client. :)

Tonight I will be resetting Beta again. I will be including the full block explorer in the update. The other included improvent will be advanced transaction sorting. You may not notice this at all but it should prevent bots from front running the AE in the future.

Here is how it works. Transactions will be sorted first by a weight algorithm which factors in the timestamp and the transaction fee. Transactions with higher fees and lower timestamps will be added to blocks sooner than those with lower fees and higher timestamps. After that, they are sorted directly by fee; transactions with higher fees are more likely to make it than those with lower fees. After that, they are sorted by amountNQT; the larger the amount NQT, the more likely they are to get in. After that, they are sorted by how many bytes they contain; the more bytes, the more likely they are to get in. Finally, if everything else is equal, they are sorted by transaction ID in ascending order; the lower the transaction ID, the more likely they are to get in.

There are reasons for this explained on the NXT forum here: https://nxtforum.org/general/transaction-sorting-ideas-for-the-future!/ (https://nxtforum.org/general/transaction-sorting-ideas-for-the-future!/)

Hello  stag.
You can post the the link.
thx

Updated the post with a link. :)

You guys do realize that stagflation is a very bad thing right? Pretty much all economists agree on this...

Depends on your definition. I came up with an alternate definition based on the root words. I will post a link to my explanation in a second.

Edit: https://nxtforum.org/alternate-cryptocurrencies/stag-qa/ (https://nxtforum.org/alternate-cryptocurrencies/stag-qa/)

I just read this. It seems like people with root addresses can just create a bunch of "branches\trees".

Trees are set in stone there is only a certain number of them. A single tree may have an unlimited number of branches. You can put a branch on your own tree and only on your own tree but this doesn't do you any good unless you maintain it as active which costs that account STAG to keep up. Even then, the benefit is minimal.

---

The Beta Update has happened! If you are still interested in helping me test, please send me a PM with your account ID and public key again. I don't want to do a bunch of transactions for people who aren't testing anymore.

Beta Testing, go here: http://104.131.29.158:7826

Wow! Lots of people still interested in beta! Looks like I have to send out some funds!

EDIT: Sent out funds for beta testing!

---

A list of test accounts being used for this round of Beta. Provided for your convenience (and mine)!

• STAG-DNPP-7TLC-2N46-3YSAW
• STAG-9EEN-HNVB-CLEB-D7DAP
• STAG-U5AP-4LHD-N9VM-8HVZ7
• STAG-S89B-3V9C-GHV9-5KTGV
• STAG-EA2P-84PJ-PUWB-GC6DU
• STAG-K96U-N3NP-4ZWG-4R7YT
• STAG-YD9L-4REU-TRE9-DUSDZ
• GENESIS: STAG-GA2D-C6RL-JDEG-CW2RU

any update about stake holders?

Yes, I have just been busy and haven't gotten a chance to update the list yet.  :/

one tx went trough but after that i am getting error/ am i missing something ?


https://i.imgur.com/WXr7Rr5.jpg

Same here. First transaction ok, but after that i am getting same error. After a refresh and new login it works again only once.

Send ok just message at the invoice but it's ok.

Hmmm, the could not verify signature server side is something I thought I fixed. Anyone else getting this error?

EDIT: I tested this on the local client and it worked fine. Must just be an issue with remote client access. Also, a minor announcement: I will be upgrading the UI to the latest NXT UI (mostly because it is nicer and allows you to search the marketplace easily). There will likely be new bugs after this update so be ready for a whole slew of new issues!

Tried to register an alias, same message.

Just updated the post above. It is another issue related to the remote client.

Working on overhauling Stag with the latest version of NXT. :)

You are doing a great job Stag regarding all the bugs we have been having, I will be looking forward to the full Release of STAG in due time and your ever growing support :)

Great job Stag.I test again and it's ok !

That is weird, because I haven't sent out the update yet.

I said the old version.

Ah. So I am inches away from being able to send out the new version. With it will be another blockchain reset. Hopefully I can send it out by tomorrow.

I have some good news and some not so good news. The good news is that the new update is forging just fine and I will update the node tomorrow with the latest version. The not so good news is that is all I will be able to accomplish tomorrow as I have other obligations to attend to.

This really looks promising! Good job dev.

---

The latest version of Stag Beta is now on the public node you guys are used to by now! This Version utilizes NXT 1.3.4 at its core and offers new features such as searching the marketplace for tags, description text, and title. It also has a slicker design.

It also offers a modified version of transaction sorting/execution that won't be included until NXT 1.4.0.

This method sorts unconfirmed transactions first in ascending order of height where new blocks have a height on Integer.MAX_VALUE and blocks that have been attached to a block and popped off have the height of the last block they were attached to. Next, they are sorted by TX fee per TX byte in descending order. Next they are sorted by a Bit value in descending order where the value is 1 if the transaction sender is logged into that node and 0 if they are not. After that, they are sorted in ascending order of their arrival timestamp. This is a marker indicating when the unconfirmed transaction arrived at the node forging the block. Next, they are sorted in descending order by the amount of NXT being transfered in the transaction because I am assuming that the more NXT that is transfered, the more important the transaction is. Finally, it defaults to sorting the blocks by transaction ID.

Transactions are executed and stored in the block by the arrival timestamp at the forger's node in ascending order, the height of the transaction in ascending order, and finally by transaction ID in ascending order.

As I mentioned before, I don't have time to look for bugs today so I am counting on all of you to do a good job for me!

Great job Stag i pm you if you want again bêta tester.

It took some tweaking, but I finally got it working, there was an error processing peer transactions so the two nodes blacklisted each other. I fixed it now and spent most of my day doing something I said I wasn't going to do... That is, debugging the new version of Stag...

you are doing a great job. Will check the new beta

And I forgot to change the peer requests in the blockchain processor so that new blocks don't go through. One more bug to fix today sigh.

Every action ends with "Could not verify signature (server side)".

Oops, forgot about that in the big update. Fixed now. I also figured out what was going on with the nodes not connecting. I made a typo when adding their data to the database. It should be working well now.

Failed to connect

http://104.131.29.158:7826

Same for me too

Sorry guys... Beta is down right now. I have some more debugging to do for the new beta. There was trouble verifying transactions from other nodes and I have been particularly busy so I haven't gotten a chance to work on it much. I will have plenty of free time soon though.

Thank you all for your patience!

EDIT: I will be making a new system for transaction storage to minimize the amount of space every transaction takes up in the database. It will implement alias transactions and all new accounts will get one free alias upon creation. The free aliases will start as purely numeric and will be made to be as short as possible so that they are easier to remember.

Transactions sent to an alias will take on three forms...

• Numeric: transactions sent to these aliases will be stored using the alias rather than the account ID. They will store the data as the smallest MYSQL data type possible. Values 0, or 1 will be stored as a BIT and -1 will be stored as a null BIT. Values less than -1 and greater than 1 between -128 and 127 will be saved as a TINYINT with 128 being a null TINYINT. So on and so forth for each data type. This type of transaction will be indicated by a null BIT.
• String Aliases shorter than than the length of an account ID or longer/equal ending with a number between -128 and 127: these will be saved as a character array that makes up the string alias and a byte or null if it is shorter than the length of an account ID. This will be indicated by a BIT equal to 0 In the database.
• For String Aliases that do not match the requirements of the above specification: these will be converted into the standard RS account ID saved as a BIT array which encodes to the RS account ID.

Numeric account IDs will be completely done away with. The reasoning for this is that they are only 8 bytes (64 bits) in length so there is a relatively high possibility of two passwords making the same numeric account ID which is the whole reason for public keys and public key announcements in NXT.

Stag will do away with these in favor of simply using longer RS ids (I haven't decided on a size yet) and using aliases as addresses. It will work similar to Bitcoin. Public keys will exist but it is not necessary to share them on the blockchain.

Instead, there will be a wallet file created the first time Stag is run. The account RS ID will be derived from the wallet file bytes hashed with the user's password hashed with the private key. In order to get the funds from an account you need the wallet file, the password, and the private key of the account. This decreases the chance of two passwords leading to the same account and may increase privacy (I will have to do more research).

EDIT 2: OK. I think I have come up with an idea for increasing privacy through this method. The wallet file will contain a number of private passwords... These passwords are used to generate new addresses sort of the same way Bitcoin has multiple addresses.

There will be two types of addresses, sending addresses and recieving addresses. Sending addresses are used only when sending out a transaction, they are used as a way of identifying where a transaction came from. An account has only one of these, but it changes every block. This is where brother rewards go.

Recieving addresses are permenent and every account may have as many of these as they like. They forge and block rewards are sent to them...

In a transaction, a sending address claims a particular recieving address with a special code and forwards its funds to one or more recieving addresses. Brother rewards are handled differently. They first go to a sending address, that sending address which holds the Brother Reward and forges with it. It will be the last of the accounts claimed by a future sending address.

This is ONLY speculation though. I have to think more about the benefits and pitfalls of a system like this.

Thanks for the update, Dev!

Can't wait this to launch. Do you have any launch date on your mind?

I wanted to release before the new year but if I chose to implement a Sending/Recieving address system to up privacy, it will take longer...

Thanks for updates. We will wait to have some whenever it goes live.

Just got this link from a friend: http://gas.dia.unisa.it/projects/jlbc/schemes/bgv11.html (http://gas.dia.unisa.it/projects/jlbc/schemes/bgv11.html)

It is based on RLWE encryption angorythms. If I can somehow get the code to go open source, I can use it in Stag so that it will continue to be safe even after the release of quantum computing...

EDIT: Ah ha! It is open source... Just found the repository. Will be implementing it instead of sha256.

EDIT 2: Hmmm.. This encryption algorythm seems to take an awful long time to execute even with the most basic settings. In other words... Public/private key generation will take a while. I wonder if there is any way to speed up the process by providing fixed numbers rather than relying on a generator to come up with a prime number for me...

Edit 3: it took some searching, but I finally found a list of prime numbers that contains a large number of 64 bit primes. This is promising. It contains the first  1.4 billion prime numbers. :)

Nice to see that there are still devs that really put work in to their projects.

Good job!

thread looks so clean

Had to check it thru after your post, but you are right: not much fudders around! :)

I want to pre-register.
It looks to be a nice project

Add me to the pre-register list as well.

Hello stag some news ?

initial distribution soon?

No for the moment.Wait for the list.

I think dev is preparing the list or so. Till now everything testing went as normal as to be.

I signed up for initial distribution at the very start, there was a list and now it seems to be gone... Please honor the Original list when STAG release comes about  :)

I was in that list too. i hope i still are in it!! :)

This look very promising when you check how much time and work the dev has put in this.

i want to be part of the initial pre-registration.
Thanks.

Don't stress guys !

Hey everyone! Just wanted everyone to know that I am still around! I have been in contact with a nameless dev working on an advanced anonymity network combining Tor, i2p, and advanced encryption techniques to make it really difficult to track users. He/she has been giving me information and code for it so I have been considering integrating Stag into it to protect Stag users from unwanted spying.

Does this sound like a good idea to people?

I think it's good idea. Takes your time and Merry christmas stag.

Sounds GREAT! Merry Xmas to you!

Merry Christmas to everyone and wish you all wonderful time.

i want to be part of this.

Thanks

Read in page one in red.

thx

Well this depend on your activity if till distribution starts somehow you achieved the Sr.Member Status then you will qualify for free . This was rule at start now may be this continue.

Algo?

Welcome 2015 ! Happy New Year to all of us . New year new things , new ideas and new luck . let's go ahead !

Happy New year to everyone.

Happy New year guys !

How is going development of this coin ? any news ? When can this be purchased on some exchange ? Keepin eyes on this one.  Happy New Year y'all.

waiting for news.

It seems that it will be ninja launched because it is down for testing for so long. May be I am wrong but it's my impression about Stag.
Anyway sooner dev will update us about current situation.

Maybe it will be ninja...
Start was great, we was informed about development, even involved, but now is so quite...

He is developing. will b back in few days  with new ponzi scheme

I heard here in some threads about ponzi a lot. I really don't know what ponzi represent any explanation would by helpful to understand the meaning of this word.

https://en.wikipedia.org/wiki/Ponzi_scheme

Could you explain how you see this as a ponzi scheme?

Thanks!

Just wanted to let everyone know that I am still alive and haven't given up yet. Production is on hold for a little bit though. I am working on developing the anonymity network with ZenSage first because Stag will involve heavy integration into his combined i2p/Tor network. I cannot do much with Stag until this is complete and I have the proper API. That is why you haven't heard much from me lately

Further, sStag will go through a sort of rollback in the code once I do pick up production. The Devs at NXT have been busy releasing a lot of new features and optimizing their code. I want to include the latest features in Stag (such as regex transaction message parsing verifying the sender of a message and issuing Monetary System coins on top of Stag). This will, of course happen when the anonymity network is ready to be integrated.

Thank you all in advance for your patience and understanding!

Thanks for the update! will be patiently waiting. good luck.

This updates from Dev is very good and it will keep the community active on this thread. We support you dev to bring something new in cryptoworld. Keep it up  ;D

Still watching this one.

We all need to keep watching this thread because dev will come and just announce the launch of Stag. Dev is busy in development and preparing surprise for us all.  :D

I am very excited , I think till Stag will be out my status will be of Sr.Member and I could be one of the persons those who receives the stag. Just little time and I am going to be eligible for this. cheers ;D ;D ;D

I will be happy for you but I think dev is coming out sooner with surprise launch . Good luck mate for your wish.

Dev is working on some most advanced and stable technology to bring something totally new. This will bring huge change in cryptoworld.

algo?

Any update on this project?

This is time to be updated in order to keep the thread active and catch attention of future investors.

Nope, still working on other projects to insure integration. Also, I have been brought on by SuperNet to work on turning a very complex price pegging algorithm into code. I plan to use the bounty for this to bring on some additional help to Stag and the anonymity network. (It is a very big bounty I am working towards).

Also looking into blockchain integrated wallet files for other coins. The idea is that, something like a Bitcoin wallet, could be stored on the Stag blockchain if it is encrypted well enough and allow a user to make Bitcoin transactions from within the Stag platform without depending on a pegged asset or MSCoin. Also looking into account pruning to increase the amount of time accounts can remain disposable given a particular key size. It would work by deleting accounts that have been inactive for very long periods of time (say 100 years) and allowing that account's public key to he reused.

Because a Stag user's balance is split into multiple disposable accounts (as is the new plan), it is considered highly improbable that anyone would hold onto a private key for 100+ years to steal an account's balance. Further, someone trying to steal this way would have to constantly monitor the blockchain to see if that account is deleted and reactivated, then log into the account AFTER it is created again but BEFORE the account's balance is spent.

Assuming this does happen, chances are that the account has very little Stag in it making all the key saving and patience near worthless. Further, the theft is only good once as the account will not be used again for another 50 years. This makes the gain from the theft worth less than the storage space and time spent storing the key and transferring it between computers. In the mean time, the stored key is likely to get lost or corrupted before the attacker can use it.

Finally, I am investigating possible methods of interpreting statistical data automatically to help with the price stability function. This would likely require a secondary proof of work block to be done every so many blocks. This PoW would be the work of building an equation to match statistical data from cryptocurrency exchanges to determine the ideal amount of STAG per account by comparing the purchasing power of the previous ideal amount of STAG per person in LPPI (Local Purchasing Power Index) to the average cost of living in first world countries in LPPI doubled. This way there is enough STAG  per person to support 2 adults.

These are mostly just thoughts at this point. Let me know what you guys think!

Awesome words and great idea I like this very much. Everything at start is just an idea and later thoughts turn into reality. Dev you are an imaginary developer and i like your vision for future.

Dev I think it is the best way to keep the interest of people in project to post or update at least one time in week . Just my suggestion .

I agree, i made a logo for Stag, and watching this thread for 4 months, in order to be involved in Stag and get paid.
Even was the early tester. But it is too quiet now.

I will watch this. Soon I am senior member.

It is nice to see that you qualified for free giveaway just like you many members became eligible now need the coin to be released and distributed .Congratulation once again for qualifying.

Is this project still alive?

It is more than one month since last post from dev . This is the time for updates to hear about the developments on this project , Dev any news ?

Ok, logo provided by me 5 months ago, and this will not goin' anywhere.
Please pay my logo with btc, or remove it from the OP so i can sell it elsewhere. Thanks.

I think it's clear now.  :(

Did you get your payment?

Such promise, all hopes faded now.