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!

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.

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.

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.

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!

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).

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!

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.

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.

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


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

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.

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!

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

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.

Not at all too late, send me a PM.

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!

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

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

Stag is a cryptocurrency based on the NXT source code (written in java). It is a cryptocurrency intended to be (relatively) stagflationary rather than inflationary like fiat currency or deflationary like every crypto I am aware of. I have already written out the equations necissicary for this.

As a core dev you will be responsible for modifying the NXT code to implement these equations, create the Stag genesis block, and modify the http and Json calls so that it runs seperatly from the NXT network.

I personally know Java but I cannot commit a lot of time to developing Stag at the moment so I am looking to hire a core Dev.

Stag will be distributed freely to as many people as want in the initial distribution. The number of people directly correlates to the amount of Stag released at initial release (100,000 Stag per person). 5% of the initial distribution has been set aside. 2% for myself to use as bounties after release (and because I need money) and the other 3% to be used as bounties before initial release (website development, logo creation, core development, forum creation, etc.)

As the core Dev, you will be given a 0.8% of Stag's initial distribution in addition to the 95,000 Stag everyone gets. Which, given the amount of interest Stag has generated so far, would be quite a lot of Stag. (I got over 50 people who were Sr. Members or Hero Members interested in the initial distribution in under 12 hours).

In most cases, you have to be at least a Senior Member to get in on the initial distribution, however, people who claim bounties are exempt from this rule so anyone can be a core dev.

Please let me know if you are interested or point people who are good with Java in my direction.

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.