good news, I have lobbied to add NXT on https://www.litebit.eu/
NXT will be ADDED NEXT WEEK !!!!
this is big becausse you can buy NXT with mistercash, ideal, etc...
this is a new gateway to fiat also. MARKETING, GO PROMOTE IT PLS
Pin
NXT: 12088507821025750338
Topic: NXT :: descendant of Bitcoin - Updated Information - page 533. (Read 2761624 times)
My installer downloads and installs Java when you install Nxt if you don't already have, exactly like you said it shouldn't because of admin rights...which I agree with. Since Nxt requires Java, though, this was by far the most user friendly solution. Over 5,500 downloads and I've only seen 3 or 4 people(that have contacted me) that had issues.
Unpacked JRE can be embedded into installer, and installed without admin rights. But it requires to create installers for each platform you support.Double edged sword. I considered this but decided that most people will have Admin rights to their machine so downloading for the most part shouldn't be an issue......where as expecting people to know if they have x64 or x86 architecture and Win7/Win8 didn't seem like a good solution.
I chose to make a "one size fits all" installer rather than complicate matters.
What if some newest release of NRS will require newer version of Java? Will you check what version user have installed?
Embedded JRE is always considered as good solution for serious Java-based software.
Considering architecture: NRS is not required to run with x64 JRE since it doesn't require too much memory. Embedded x86 JRE work perfect in x64 Win. And there's no different JRE versions for different Windows.
Still do not know anything about *nix and OSX.
Is there any specification on the Pooled Forging that you could make available? As in the API call specifically or how it works?
I'm thinking of it, any proposals?
I was thnking about 2 options:
OPTION 1:
1) High level API call from account "A" to assign/remove right to forge to account "B" as well as split between prize
2) If block is found then prize is split between "A" and "B" according to agreed split
3) If prize cannot be split (because block had 1NXT and we can't have less than 1 NXT in an account) then what?
OPTION 2:
1) High level API call from account "A" to assign/remove right to forge to account "B"
2) If block is found, then account "B" gets the prize
With option 2 then account "A" needs to trust account "B", as there's no guarantee that they will pay back the prize earned
Comments?
ps.: I'll have to be offline for a couple of hours.
There could be a reasonably limit set on accounts one can forge for, this will naturally limit the size of a specific pool, though nothing prevents the same pool operator from making many forging pools. At least having a fixed limit on accounts that can be pooled together allows the NXTcore to make reasonable tradeoffs in coding this.
So, the API call would have enable pooling with acct # and payout threshold of X. And another to stop pooling, which would probably release any accumulated funds. Whatever fractional NXT is left would end up with the account that does the pooling. When fractional NXT is supported, then this dust problem goes away.
James
Just got access rights to bitbucket repository :-)
I will probably submit in a few hours as I need to finish some new functionality first!
I will probably submit in a few hours as I need to finish some new functionality first!
My installer downloads and installs Java when you install Nxt if you don't already have, exactly like you said it shouldn't because of admin rights...which I agree with. Since Nxt requires Java, though, this was by far the most user friendly solution. Over 5,500 downloads and I've only seen 3 or 4 people(that have contacted me) that had issues.
Unpacked JRE can be embedded into installer, and installed without admin rights. But it requires to create installers for each platform you support.Double edged sword. I considered this but decided that most people will have Admin rights to their machine so downloading for the most part shouldn't be an issue......where as expecting people to know if they have x64 or x86 architecture and Win7/Win8 didn't seem like a good solution. It also keeps the size of the installer to 524kb for those that don't need Java as opposed to a larger download.
I chose to make a "one size fits all" installer rather than complicate matters.
My installer downloads and installs Java when you install Nxt if you don't already have, exactly like you said it shouldn't because of admin rights...which I agree with. Since Nxt requires Java, though, this was by far the most user friendly solution. Over 5,500 downloads and I've only seen 3 or 4 people(that have contacted me) that had issues.
Unpacked JRE can be embedded into installer, and installed without admin rights. But it requires to create installers for each platform you support. 
I wish we had something like this
https://bitcoin.org/en/choose-your-wallet
Separated between "mobile", "desktop" and "web" clients along with recommended "easy" install clients all located on the home website of the crypto(bitcoin). Could add things like Requires Java or not too.
We could always say for now "recommended for beginning users" and then link to whatever client we decide on.
When I started to look at bitcoin the reason I didn't give up right away was because that website gives everything so simple and easy to understand basically anyone would be able to understand how to start bitcoin up. I chose multibit when I first started because it said easy to use...
as a new user I didn't even know how to get Bitcoin let alone hold it somewhere. Didn't hear of Coinbase, etc. till I read a forum, didn't hear of any of these wallets till I read the main Bitcoin site. K.I.S.S.
https://bitcoin.org/en/choose-your-wallet
Separated between "mobile", "desktop" and "web" clients along with recommended "easy" install clients all located on the home website of the crypto(bitcoin). Could add things like Requires Java or not too.
We could always say for now "recommended for beginning users" and then link to whatever client we decide on.
When I started to look at bitcoin the reason I didn't give up right away was because that website gives everything so simple and easy to understand basically anyone would be able to understand how to start bitcoin up. I chose multibit when I first started because it said easy to use...
as a new user I didn't even know how to get Bitcoin let alone hold it somewhere. Didn't hear of Coinbase, etc. till I read a forum, didn't hear of any of these wallets till I read the main Bitcoin site. K.I.S.S. @Jean-Luc
Would it be possible to include wesleyh´s webclient in your releases instead of the webui we have now?
Would it be possible to include wesleyh´s webclient in your releases instead of the webui we have now?
also good solution, than mistafreeze can just update his installer and we are done.
This is by far the cleanest, easiest solution.
I believe that all the other clients currently have their own installers, and I doubt that they used the same environment as I did to create them. That said, there is no reason they can't easily incorporate the same functionality into their installers.
I sent a message about this to JL yesterday, today he replied:
Quote
Btw, would you like my client to be included in the next experimental release or something? Since the current version does not have the asset exchange, people can’t really test with it. Could be placed in a subfolder of the tools, so that pepole can still access regular client at :7875 and my test client at :7876/dev or something.
Quote
Let's work on that. What is your bitbucket account? It will be easier
if I give you access and you commit your files so that I always get
your latest changes when packaging a release.
And it will be better to have it accessible at top level on port 7876,
with the current tools put under :7876/tools/.
if I give you access and you commit your files so that I always get
your latest changes when packaging a release.
And it will be better to have it accessible at top level on port 7876,
with the current tools put under :7876/tools/.
Now that is some great news!!
I sent a message about this to JL yesterday, today he replied:
Excelent news! My Nxt installer will download and install Java on the initial click if needed, no restart
If it exists, what we are talking about?
Quote
Let's work on that. What is your bitbucket account? It will be easier
if I give you access and you commit your files so that I always get
your latest changes when packaging a release.
And it will be better to have it accessible at top level on port 7876,
with the current tools put under :7876/tools/.
if I give you access and you commit your files so that I always get
your latest changes when packaging a release.
And it will be better to have it accessible at top level on port 7876,
with the current tools put under :7876/tools/.
Again Wiki should be rewritten completely.
Me clicking on too many things an losing track of where I am.
My installer downloads and installs Java when you install Nxt if you don't already have it, exactly like you said it shouldn't because of admin rights...which I agree with. Since Nxt requires Java, though, this was by far the most user friendly solution. Over 5,500 downloads and I've only seen 3 or 4 people(that have contacted me) that had issues.
The link is in my signature.
Mistafreeze and marcus03,
Do you see any possibility to combine the best of both worlds to 1 installer?
thanks
My client is a thin client, so it does not need NRS and/or Java. It's "unzip and run the exe".
It currently doesn't have an installer, but I'll probably add one later for the more professional look.
My Nxt installer will download and install Java on the initial click if needed, no restart
If it exists, what we are talking about?
Quote
Let's work on that. What is your bitbucket account? It will be easier
if I give you access and you commit your files so that I always get
your latest changes when packaging a release.
And it will be better to have it accessible at top level on port 7876,
with the current tools put under :7876/tools/.
if I give you access and you commit your files so that I always get
your latest changes when packaging a release.
And it will be better to have it accessible at top level on port 7876,
with the current tools put under :7876/tools/.
Again Wiki should be rewritten completely.
Could you please link the client for reference?
My Nxt installer will download and install Java on the initial click if needed, no restart
If it exists, what we are talking about?
Quote
Let's work on that. What is your bitbucket account? It will be easier
if I give you access and you commit your files so that I always get
your latest changes when packaging a release.
And it will be better to have it accessible at top level on port 7876,
with the current tools put under :7876/tools/.
if I give you access and you commit your files so that I always get
your latest changes when packaging a release.
And it will be better to have it accessible at top level on port 7876,
with the current tools put under :7876/tools/.
Again Wiki should be rewritten completely.
@Jean-Luc
Would it be possible to include wesleyh´s webclient in your releases instead of the webui we have now?
Would it be possible to include wesleyh´s webclient in your releases instead of the webui we have now?
also good solution, than mistafreeze can just update his installer and we are done.
This is by far the cleanest, easiest solution.
I believe that all the other clients currently have their own installers, and I doubt that they used the same environment as I did to create them. That said, there is no reason they can't easily incorporate the same functionality into their installers.
I sent a message about this to JL yesterday, today he replied:
Quote
Btw, would you like my client to be included in the next experimental release or something? Since the current version does not have the asset exchange, people can’t really test with it. Could be placed in a subfolder of the tools, so that pepole can still access regular client at :7875 and my test client at :7876/dev or something.
Quote
Let's work on that. What is your bitbucket account? It will be easier
if I give you access and you commit your files so that I always get
your latest changes when packaging a release.
And it will be better to have it accessible at top level on port 7876,
with the current tools put under :7876/tools/.
if I give you access and you commit your files so that I always get
your latest changes when packaging a release.
And it will be better to have it accessible at top level on port 7876,
with the current tools put under :7876/tools/.
@Jean-Luc
Would it be possible to include wesleyh´s webclient in your releases instead of the webui we have now?
Would it be possible to include wesleyh´s webclient in your releases instead of the webui we have now?
also good solution, than mistafreeze can just update his installer and we are done.
This is by far the cleanest, easiest solution.
I believe that all the other clients currently have their own installers, and I doubt that they used the same environment as I did to create them. That said, there is no reason they can't easily incorporate the same functionality into their installers.
Java should not be integrated into Nxt client. No installation that requires admin rights!
for mass adoption:
If average joe must even click one time more to install NXT then install BTC, LTC of whatever other coin.... they will install the easiest one.
so forget mass adoption if it is even 1 click more complicated than other coins for installation.
My Nxt installer will download and install Java on the initial click if needed, no restart
then how come nobody use them and people don't know about them?
This is actually a fair question. I think the answer is that there are MANY clients, and people generally want a recommendation for ONE. Nobody wants to rally behind one to the exclusion of others, so we arrive at a dilemma.
The key here, sadly, is for the "getting started" tutorials to focus on ONE, and then let people know there are many other options. Right now, it's a choice paradox: when presented with many great options, people are left unable to make a decision. This is a proven aspect of human behaviour.
Exactly!
I couldn't say it better.
We are too much decentralised if it's about the client.
We need to chose one and make instructions or something. We don't need to call it official.
Just choose one so everyone can post that specific client as first. And if users are interested in other clients, we can redirect them.
It is very confusing right now.
Almost every coin has 1 wallet.
Will you be able/available to do it? Who should be in charge of this?
I don't see a problem with a private site basically endorsing only one client to keep it clear for new users.
They could still mention the other ones, but could put one client (doesn't matter to me which) BIG on front, so people will mainly go to that one.
These things don't need to be decided by all people. Site owners can and probably should decide this by themselves.
What average people do;
1. Open Google
2. Search NXT, NXT wallet
3. Click at the first website
4. Download the wallet
Result; NRS wallet appears on their desktop.
5. Cannot install
6. Delete
7. never look at it again
Aaaaannnd we lost another potential investor in NXT
So I really think that all the website's should use the same clients.
Maybe even two. One simple client just to make transactions. And another one with full options like AE, Forging, Alias etc
+1 added 7
Thanks. That's a good point.
I have an idea to win those "Never look at it again" people back. Posted it many times.
When we choose one or two clients > Promote it like hell (We have to update all NXT websites with those clients). With giveaways like; Download the client, post your address and get some free NXT would win investors we lost since november but also attract new investors.
With these really simple steps we will also create more 24/h volume and more people forging > more secure network.
Conclusion; We produced so much together. We have to get our shit together and present ourselves.
Is there any specification on the Pooled Forging that you could make available? As in the API call specifically or how it works?
I'm thinking of it, any proposals?
I was thnking about 2 options:
OPTION 1:
1) High level API call from account "A" to assign/remove right to forge to account "B" as well as split between prize
2) If block is found then prize is split between "A" and "B" according to agreed split
3) If prize cannot be split (because block had 1NXT and we can't have less than 1 NXT in an account) then what?
OPTION 2:
1) High level API call from account "A" to assign/remove right to forge to account "B"
2) If block is found, then account "B" gets the prize
With option 2 then account "A" needs to trust account "B", as there's no guarantee that they will pay back the prize earned
Comments?
ps.: I'll have to be offline for a couple of hours.
It works as in option 2.
So if it's already coded, do you already have the API specs?
Pinarello how are things standing in the eMunie area? Are you still following them?
Is there any specification on the Pooled Forging that you could make available? As in the API call specifically or how it works?
I'm thinking of it, any proposals?
I was thnking about 2 options:
OPTION 1:
1) High level API call from account "A" to assign/remove right to forge to account "B" as well as split between prize
2) If block is found then prize is split between "A" and "B" according to agreed split
3) If prize cannot be split (because block had 1NXT and we can't have less than 1 NXT in an account) then what?
OPTION 2:
1) High level API call from account "A" to assign/remove right to forge to account "B"
2) If block is found, then account "B" gets the prize
With option 2 then account "A" needs to trust account "B", as there's no guarantee that they will pay back the prize earned
Comments?
ps.: I'll have to be offline for a couple of hours.
It works as in option 2.
So if it's already coded, do you already have the API specs?
Jump to: