NXT :: descendant of Bitcoin - Updated Information

[jl777]

I don't think anybody has disagreed with the 3 million NXT from unclaimed funds for marketing. Do you want to continue managing that by running polls, etc. or would you rather delegate that to someone else?

I prefer to delegate that to someone else.

We already reached consensus about authorizing 3 million NXT for marketing. It is now just a matter of regular disbursements, so please choose NXTcommunityfund or salsacz or landomata or somebody else to manage the disbursements. Repolling again and again for already authorized funds in inefficient.

We can still do all that for the remaining 6 million NXT, though I think we should set aside 1 million of that to NXT servers.

James

[1715396339]

1715396339

[1715396339]

1715396339

[1715396339]

1715396339

[1715396339]

1715396339

[Asian Prepper]

Please upload me a version, I beg of you... I spent the whole day... still on forks... WTF...

I have only web access to these nodes, no ftp, sorry.

Is my client correct now? after the new reinstall?

56577      4747512364439223888      Sunday, February 02, 2014 12:48:41 PM   
      
      0      0 + 0      0 B   
      
      2      11369686551132252224      467 %

yes right branch

Thanks for the confirmation bro.

[joefox]

Qbtc is rreferring to the www.nxtcrypto.org site.  She should not have to pay the fefees out of pocket.  Come on people.  Same for joefox on wiki and btc24 on forums and intel for info/download.
Marketing fund.

I We sent 50k + 5k for wiki to cover for last 2 months from the NxtMarketing. There is also a small support for new sites from these funds and there would be support for most important sites that also provide new content... Most important are consultations.. this page is not optimal for new users: http://www.nxtcrypto.org/nxt-coin/client-download but new clients would hopefully solve it

I agree with salsacz here.  He's given my a much-needed bounty fund to use for wiki translations, and those rewards have been sent out for work done in December and January.  The presence of the fund has driven more interest in translation, which furthers our goal of getting more international reach.  The front page of the wiki is now available in 16 languages.

I am comfortable with how I've been rewarded for the wiki and most of my other work; I can almost cover my costs (not including time) so I'm not too concerned there.

Work on a podcast is coming along, and I am continuing to produce the "Nxt minutes" for the Let's Talk Bitcoin podcast.  A thread for feedback and comment on those minutes will appear on the nxtcrypto forums very shortly.  

I have already put out a call for contributors to the podcast, and thanks to an interview that's about to start, and gracious permission from Tai Zen to use audio from his excellent interview with Anon136, we've got enough to put together a solid first episode.  So stay tuned.

[Uniqueorn]

I don't think anybody has disagreed with the 3 million NXT from unclaimed funds for marketing. Do you want to continue managing that by running polls, etc. or would you rather delegate that to someone else?

I prefer to delegate that to someone else.

We already reached consensus about authorizing 3 million NXT for marketing. It is now just a matter of regular disbursements, so please choose NXTcommunityfund or salsacz or landomata or somebody else to manage the disbursements. Repolling again and again for already authorized funds in inefficient.

We can still do all that for the remaining 6 million NXT, though I think we should set aside 1 million of that to NXT servers.

James

Told ya

[Uniqueorn]

I definitely think that the fund should be split up into 5 or whatever members of committee so that we can be 100% sure noone steals any. Letting 5+ different people have access to the fund could easily lead to one of them stealing.

[Merin]

Well hello,

i´m a long time lurker but stay in nxt since December. Unfortunately I´m very busy and have no time to read the whole thread. I´m fascinated about nxt but my mind was blown away as c-f-b announced “Lakshmi”.

Some quotes from c-f-b:

It will be a PoW coin. So one of the additional functions: Nxt will be adopted by hardcore miners.

Lakshmi uses Nxt blocks. U generate only coins. And this requires 1 NXT fee to store the info in Nxt blockchain via AM.

U mine more LAK if u have more visitors on ur site. Yes, it's Google AdSense killer, people prefer to generate coins instead of watching ads.

It's a PoW-coin, based on Nxt AM. This coin is protected against 51% attacks by Nxt PoS algo.

U can place LAK miner instead of banners to earn money.

Lakshmi project is postponed for the time being. Yulkisa has some problems related to legality of her site, so she can't take part in Lakshmi development right now.
I could consult for free if someone else wants to launch a similar coin. Just create a new thread and post the link here.

-------------------------------------
The last quote makes me sad.
I´m not sure if all realize the possibilities of a coin like LAK on top of the nxt network.
You know KimDotcom´s project Baboon?

http://www.nme.com/news/various-artists/72606

He claims to have secured several million in funding for a project, which will give the public access to free music, compensating artists through advertising revenue. A paid-for version is also planned, giving fans the chance to listen to music ad-free for a fee.

Imagine a project like this based on Lakshmi or a similar coin. Or a streaming games site like twitch.tv. The possibilities are endless and maybe a big step to create mass adoption  through entertainment related projects.

Please consider the option to use the unclaimed nxt coins to fund and develop “Lakshmi”, maybe with a new name, and related projects on top of NXT.
So many skilled people are part of this community, I´m sure you are able to do this!

Thank you all and keep up the good work!

Merin

[jl777]

I definitely think that the fund should be split up into 5 or whatever members of committee so that we can be 100% sure noone steals any. Letting 5+ different people have access to the fund could easily lead to one of them stealing.

We should just use BCNext's solution, but using trust instead of hardcoding acct numbers in the NXT core.

5, 7, 9, 10 people probably doesn't matter too much.

Also, funding decisions needs to be separate from disbursement to remove conflict of interest.

We need trusted people to hold the funds and then separately experts in each field to determine how to spend the funds. This is how I setup the NXTcommunityfund, except I am probably not an expert in any field.

James

[Coinonaer]

A PoW-Coin on Top of Nxt would help us. Lakshmi or something similar should be developed further.
Even if it cost 1 Million of the unclaimend funds!

[xyzzyx]

Actually using ZLIB might not be the best idea, better would be something that's faster.
I'd go with LZ4. There's also lzturbo, but, lz4 has format that might be nicer for "small devices" (raspis & Co.)

And ChuckOne is right, binary protocol equals problems

If we go with a compression, then it should be optional.  To me, a RaspberryPi isn't a small device.  A JavaCard with 80k working memory is a small device.

I'd like to re-iterate my support for a simple endian-neutral binary format.  Encode integers using the simple variable-length scheme for numerical constants as outlined in section 2.1 of The Case for Universal Symbol Files by Michael Franz [PDF here]:

Our symbol files encode constant data in a machine-independent and space-economical way. The two basic formats that are used for representing numbers and strings require a variable number of bytes on the file, and use a stop bit for denoting the last byte of a sequence. In order to keep matters simple, we purposefully represent each data value by an integral number of bytes, disregarding the potential further savings in size that might be possible if byte boundaries were transcended.

The scheme we employ for coding integers, suggested by Odersky [9], can be applied to values of any magnitude and is independent of the word length and the byte ordering of the machine used. Not only is the resulting file representation portable, but so is the algorithm, which can be used on any machine that offers 2's complement arithmetic.

The encoding and decoding is very simple and there is an example encoder given in the paper.

Don't use the format for strings outlined, however, as it assumes an 7-bit character set.  Instead encode strings and arbitrary buffers using a format similar to the storage of Pascal strings: a size integer, which uses the variable-length scheme above, followed by a string of bytes.  This would allow strings/buffers of any length.

[EvilDave]

What do I do about DGEX not honoring my withdrawal and keeping my BTC?

1st - do not troll to the general NXT thread
2nd  - contact DGEX, we have no "unhonored" withdrawals, a handful out of the tens of thousands are under investigation requiring input from customer.

Thank you

In what way is this trolling? I've been in touch with your support for more than a week and still no sign of my funds. Shame on you for taking 1.4% withdrawal fees and taking so long to process a simple Bitcoin transfer!

Elokane: this thread is intended as a central point for NXT development/marketing/whatever updates. It's not actually affiliated with DGEX in any official way. The Nextcoin.org forums are run by the DGEX crew and are a much better spot to get some attention from DGEX.

[gimre]

I'd like to re-iterate my support for a simple endian-neutral binary format.  Encode integers using the simple variable-length scheme for numerical constants as outlined in section 2.1

This is bad idea for multiple of reasons (first one being, it would be real PITA for alternative core implementations)

[Come-from-Beyond]

Instead encode strings and arbitrary buffers using a format similar to the storage of Pascal strings: a size integer, which uses the variable-length scheme above, followed by a string of bytes.  This would allow strings/buffers of any length.

Variable length types in Nxt binary format use Pascal approach.

[salsacz]

Btw, I don't see Salsa's salary in that Google doc. I hope he doesn't work for free, this is not what I expected when sent 250k.

Well, I still didn't have a time to think about this. It is the best in these cases to ask utopian/uniqueorn, or pin

[Come-from-Beyond]

Btw, I don't see Salsa's salary in that Google doc. I hope he doesn't work for free, this is not what I expected when sent 250k.

Well, I still didn't have a time to think about this. It is the best in these cases to ask utopian/uniqueorn, or pin

Then ask them, plz.

[IveBeenBit]

Should we make a poll for that?

Yes, plz. Coz if the community doesn't come to a consensus even on this then the coin will be sent to the genesis.

community voted not to send them back to genesis....funding committee will manage the funds....the longer the committee takes to arrange itself....the less funds they will get from you to manage.

When did this happen? Sending leftover money to the genesis account is a good idea. Otherwise, we start to look like a government with lobbyists and different interests all politicking to get a piece of a pie that doesn't belong to them.

There may be better ways to handle the money, but without some sort of super majority, I think it should be burned. Keep in mind that by burning the money, there is no net loss of wealth to the Nxt ecosystem. Every NXT becomes more valuable after the burning and it all balances out.

There are probably 3-4 million bitcoins lost forever from early miners, and every other bitcoin gains value because of that. It's no big deal.

Personally, the only thing I can think that would be better than burning it would be to distribute it to smaller accounts to help counter the criticisms about distribution that plague Nxt. But again...that is central planning and just an example of how power corrupts.

Edit...words.

[NxtChg]

https://i.imgur.com/ocSGxIJ.png

The encoding and decoding is very simple and there is an example encoder given in the paper.

Don't use the format for strings outlined, however, as it assumes an 7-bit character set.  Instead encode strings and arbitrary buffers using a format similar to the storage of Pascal strings: a size integer, which uses the variable-length scheme above, followed by a string of bytes.  This would allow strings/buffers of any length.

Is it really necessary? How much is he gonna save, especially since he still rounds to bytes and doesn't use compression?

And messing with bits is even worse than dealing with endianness.

I think either compressed JSON or a simple binary format would be enough.

[brooklynbtc]

In regards to the unclaimed coins, what if we set up one mother of a faucet. fund that thing for months 

[xyzzyx]

I'd like to re-iterate my support for a simple endian-neutral binary format.  Encode integers using the simple variable-length scheme for numerical constants as outlined in section 2.1

This is bad idea for multiple of reasons (first one being, it would be real PITA for alternative core implementations)

In what way?

[ChuckOne]

Actually using ZLIB might not be the best idea, better would be something that's faster.
I'd go with LZ4. There's also lzturbo, but, lz4 has format that might be nicer for "small devices" (raspis & Co.)

And ChuckOne is right, binary protocol equals problems

If we go with a compression, then it should be optional.  To me, a RaspberryPi isn't a small device.  A JavaCard with 80k working memory is a small device.

I agree, that's why I'd like the idea of an additional layer. Turn it simply on or off at your convenience.

I'd like to re-iterate my support for a simple endian-neutral binary format.  Encode integers using the simple variable-length scheme for numerical constants as outlined in section 2.1 of The Case for Universal Symbol Files by Michael Franz [PDF here]:

Our symbol files encode constant data in a machine-independent and space-economical way. The two basic formats that are used for representing numbers and strings require a variable number of bytes on the file, and use a stop bit for denoting the last byte of a sequence. In order to keep matters simple, we purposefully represent each data value by an integral number of bytes, disregarding the potential further savings in size that might be possible if byte boundaries were transcended.

The scheme we employ for coding integers, suggested by Odersky [9], can be applied to values of any magnitude and is independent of the word length and the byte ordering of the machine used. Not only is the resulting file representation portable, but so is the algorithm, which can be used on any machine that offers 2's complement arithmetic.

The encoding and decoding is very simple and there is an example encoder given in the paper.

Don't use the format for strings outlined, however, as it assumes an 7-bit character set.  Instead encode strings and arbitrary buffers using a format similar to the storage of Pascal strings: a size integer, which uses the variable-length scheme above, followed by a string of bytes.  This would allow strings/buffers of any length.

--- off topic ---
Besides real problems regarding binary formats, its psychologically most destructive property is that everybody has the self-proclaimed best encoding, the fastest encoding, the most space-efficient encoding, the most flexible encoding and so and so which only differ in one of two bits somewhere and therefore makes them 100% incompatible. Thank you.

Why? Because binary is the way to go if you want fast, efficient, direct, buzzword, buzzword, ....

Look at text-based format. Do all these requirements matter there? No. Their implementors focused primarily on the content in conjunction of readability, maintainability, flexibility, expandability and independence. All properties, which are required for the maintenance of long-term applications.

[Fatih87SK]

Let me know if I can do something more. If you like it I can give you the 3d model.

I like ur pic but I asked for ivory on slate with ornament on the border for that amount.

Sorry for asking too much questions :p Do you mean like this (sketch);