NXT :: descendant of Bitcoin - Updated Information

[opticalcarrier]

So I've been having trouble setting up a node under Debian.

This is the error I get after 0.8.3 starts:

./run.sh: line 1:  3004 Killed                  java -Xmx1024M -cp nxt.jar:lib/*:conf nxt.Nxt

Help is appreciated.

did you use apt-get to install java?  give us output from "uname -a" and "which java" and "java -version"

[1715385270]

1715385270

[1715385270]

1715385270

[1715385270]

1715385270

[1715385270]

1715385270

[1715385270]

1715385270

[lyynx]

Not sure if someone posted this yet, but we need this type of exposure. Begin watching at 12 minute mark http://www.youtube.com/watch?v=hdAnyC45ZbU

[xyzzyx]

Suggested NIP (Nxt Improvement Proposal)

Adding "meta information" to Arbitrary Messages.

As AMs are going to become a key communication tool for various other parts of the Nxt system (including NIPs themselves) I suggest that we decide on one of the two ways of providing minimal "meta" information for AMs.

This could be done in the following 2 ways:

1) Encode them as URIs (making it simple for web apps to handle different kinds of things).

or

2) Use the first x bits of the AM to indicate the type.

I like the 2nd suggestion: a type-tag.

While not terribly important, I would like to see the type-tag be 1) human readable 7-bit ASCII, and 2) allowed to be of variable length.  

Edit: and if an AM does not conform to the above, that's ok.  AM might be used for encrypted payloads where you might not want all others to know what exactly it is for.

[rickyjames]

NXT FUNDING COMMITTEE VOTE IS NOW UNDERWAY UNTIL 12:01 AM MARCH 8 (UTC)

Per our previous poll, all three committees (NXTmarketingfund, NXTtechdevfund and NXTinfrastructure fund) will consist of five elected members.

Read candidate statements here:

https://bitcointalk.org/index.php?topic=479167.msg5280476#msg5280476

Background:

https://bitcointalk.org/index.php?topic=345619.msg5280786#msg5280786

DETAILS ON VOTING :

EVERY NXTer WITH AN ACCOUNT STARTED BEFORE FEB 21 GETS TO VOTE ON ALL THREE COMMITTEE BALLOTS.

If you want to vote, send me a PM with just the word VOTE in the title.  I will respond with your password and the voting site URL.  I will know who voted but I will not know who you voted for.

LIVE ONGOING VOTE RESULTS:

https://www.electionbuddy.com/elections/12343/results/t34ayqhm2

Update:  At 28 hours into the vote I have distributed 98 ballot access codes so far to nominees, candidates, and PM requestors.  I have vetted all PM requesters and have found all to be legitimate eligible NXTers with two exceptions: NXT-LILY and GT-R.  These two NXTers have created their accounts since the election was announced and so I will not be sending them ballot codes.  (See, I am checking.  Sorry, you two).   I have no pending PM requests for ballot access codes at this time.  I have received no unique requests to vote from nextcoin.org or nxtcrypto.org, only one that was also posted here on bitcointalk as well.  

At this time 58 of the 98 ballot access codes I have distributed have been used to vote.  

My intention is to continue distributing ballot access codes during the voting period to users of this thread based on newcn's most recent list of most active posters (see https://bitcointalk.org/index.php?topic=345619.msg5456233#msg5456233 ) .  Most active posters will get ballot access codes first.  I have a limit of 500 ballots, we will see how many of those I get distributed over the week to come.

[lyynx]

Hi guys

Congratulations with NXT! Really great job of you all!

I made a video why I invested half my bitcoins into NXT. Hope u like it.

http://youtube.com/watch?v=ruYAxKeWxnM


(I'm an early investor in Bitcoin, see all my video's here: http://www.youtube.com/user/Marcdemesel/videos?shelf_id=1&view=0&sort=dd)

Great job, great vid.

[lyynx]

i find it hard to believe that i only posted in this thread 83 times

83 is two month ago, now it is 527!

How hard would it be to bump this from 100 people to 300 or even 500 people?  I am looking for involved NXTers to send these ballot codes to...

the list is actually 1018 lines long, I cut it to only 100, the following is top500:

Code:

   rank npost   id
     1	4541	Come-from-Beyond
     2	1224	jl777
     3	1042	pinarello
     4	981	smaragda
     5	884	landomata
     6	857	bitcoinpaul
     7	768	opticalcarrier
     8	748	salsacz
     9	724	Damelon
    10	665	laowai80
    11	662	utopianfuture
    12	589	wesleyh
    13	566	CIYAM Open
    14	556	ChuckOne
    15	527	Anon136
    16	523	NxtChg.com
    17	522	mcjavar
    18	502	rickyjames
    19	497	klee
    20	470	msin
    21	432	allwelder
    22	402	S3MKi
    23	400	brooklynbtc
    24	360	xyzzyx
    25	359	abctc
    26	354	EvilDave
    27	351	TwinWinNerD
    28	345	Passion_ltc
    29	336	BitcoinForumator
    30	332	swartzfeger
    31	331	ZeroTheGreat
    32	323	nexern
    33	308	gbeirn
    34	295	2Kool4Skewl
    35	281	Jean-Luc
    36	278	starik69
    37	277	ImmortAlex
    38	264	xibeijan
    39	264	EmoneyRu
    40	258	pandaisftw
    41	257	dzarmush
    42	247	marcus03
    43	210	NxtChoice
    44	208	bitcoinrocks
    45	198	instacash
    46	198	ferment
    47	193	l8orre
    48	190	Pablito89
    49	184	Uniqueorn
    50	183	Zahlen
    51	182	martismartis
    52	180	wakasaki808
    53	179	redsn0w
    54	176	davethetrousers
    55	175	chanc3r
    56	172	Bitventurer
    57	169	Eadeqa
    58	163	lophie
    59	155	gimre
    60	148	kodtycoon
    61	146	abuelau
    62	145	punkrock
    63	142	buybitcoinscanada
    64	140	timmyd
    65	137	igmaca
    66	132	joefox
    67	131	smartwart
    68	127	notsoshifty
    69	125	PeercoinEnthusiast
    70	121	bithic
    71	116	fmiboy
    72	116	bizz
    73	116	BloodyRookie
    74	113	FrictionlessCoin
    75	111	intel
    76	111	BitAddict
    77	110	LiQio
    78	109	lucky88888
    79	104	Fatih87SK
    80	101	coolfish
    81	101	GCInc.
    82	99	inkadnb
    83	97	rriky92
    84	97	newsilike
    85	95	kunibopl
    86	93	Pouncer
    87	93	CoinTropolis_JustaBitTime
    88	91	Ola
    89	90	^[GS]^
    90	89	Coinonaer
    91	88	Mario123
    92	85	superresistant
    93	85	iruu
    94	85	gs02xzz
    95	84	Emule
    96	83	Mistafreeze
    97	83	Jack Needles
    98	80	bybitcoin
    99	77	okaynow
   100	76	bidji29
   101	75	coolmist
   102	73	Chang Hum
   103	72	newcn
   104	72	greyw00lf
   105	70	OKNXT
   106	70	BaiMangal
   107	69	Sebastien256
   108	69	MyZhre
   109	67	jkoil
   110	66	apenzl
   111	66	Drexme
   112	65	Labteck
   113	64	idev
   114	64	artik123
   115	63	snowboard789
   116	63	mnightwaffle
   117	62	mr_random
   118	62	Sharky444
   119	61	yuriygeorge
   120	61	mthcl
   121	61	kwest
   122	59	zhangdu
   123	59	twistelaar
   124	59	PaulyC
   125	57	Asian Prepper
   126	57	Alias
   127	56	bahamapascal
   128	55	loopgate88
   129	55	davidoski
   130	52	mezzovide
   131	51	crazybonkers
   132	51	Jerical13
   133	50	marek3ball
   134	50	cc001
   135	50	VanBreuk
   136	49	google98
   137	49	Isildur23
   138	48	nxtgt
   139	47	seek4dream
   140	47	mikesbmw
   141	46	lyynx
   142	46	Hacer88
   143	45	Noitev
   144	45	Meizirkki
   145	45	BitThink
   146	44	delulo
   147	44	Kontakt
   148	43	Vega
   149	42	relm9
   150	42	plasticAiredale
   151	42	nov
   152	42	minusbalancer
   153	42	achimsmile
   154	41	farl4web
   155	41	SkillRoad
   156	40	voldemort628
   157	40	Secondleo
   158	40	McDoxy
   159	39	Voluntold
   160	38	nakaone
   161	38	User705
   162	38	Kodoka
   163	38	IveBeenBit
   164	38	BrianNowhere
   165	37	admiral.fu
   166	37	Patel
   167	36	subSTRATA
   168	36	LightningFury
   169	35	verymuchso
   170	34	sparta_cuss
   171	34	ebereon
   172	34	MarvellousMutant
   173	33	DrearyUrbanite
   174	32	zorke
   175	32	vanea84
   176	32	Forobitcoins
   177	31	pmabdsf
   178	31	nxtru
   179	31	bitdraw
   180	31	2X84
   181	30	omo
   182	30	JohnyCrypt
   183	30	Framewood
   184	29	vintagetrex
   185	29	nxtsky
   186	29	freigeist
   187	29	btc2nxt
   188	29	bitme
   189	28	longzai1988
   190	28	grandpa_seth
   191	28	antanst
   192	28	Hegemon
   193	27	aldrin
   194	27	Conurtrol
   195	26	ifightformerkel
   196	26	grex
   197	26	garcias
   198	26	cryptolawyer
   199	25	mkmen
   200	25	lr127
   201	24	jadedjack
   202	24	erik__
   203	24	NxtMinnow
   204	24	Mises_77
   205	24	Kattywampus
   206	23	yan83
   207	23	swansong
   208	23	lurning
   209	23	eid
   210	22	xgc
   211	22	tk808
   212	22	nnn
   213	22	gorgorom
   214	22	colinistheman
   215	22	Timetwister
   216	22	Ezravdb
   217	21	mindtomatter
   218	21	MadCow
   219	20	windjc
   220	20	btc24
   221	20	artila
   222	20	CrazyEyes
   223	20	CoinBuzz
   224	20	Buratino
   225	19	miramare
   226	19	matt4054
   227	19	gvans
   228	19	Daedelus
   229	18	psybits
   230	18	podyx
   231	18	morningtime
   232	18	mercenar1e
   233	18	maco
   234	18	josephliton
   235	18	gradis
   236	18	drsnuggles
   237	18	Fern
   238	18	Ebrelus
   239	18	DLXS
   240	17	yassin54
   241	17	xcn
   242	17	visaco
   243	17	giveBTCpls
   244	17	eB101
   245	17	SZZT
   246	17	QBTC
   247	17	Ardolafat
   248	16	tman10
   249	16	ricot
   250	16	pastet89
   251	16	ninjaboon
   252	16	nadrimajstor
   253	16	mingophoria
   254	16	manrus
   255	16	kknk808
   256	16	evanxxx
   257	16	bitmadaboutcoin
   258	16	KLONE
   259	15	wizzardTim
   260	15	w4llace
   261	15	neer.g
   262	15	markn
   263	15	kpax7788
   264	15	hypersire
   265	15	getfun12345
   266	15	garp
   267	15	blackfyre175
   268	15	alrose
   269	15	Mac Red
   270	14	tylerbrad85
   271	14	killver
   272	14	dr_yan_yan
   273	14	alex0909
   274	14	ViktorK
   275	13	user1922
   276	13	trefifund
   277	13	sherpico77
   278	13	r3animation
   279	13	pabloangello
   280	13	luckygenough56
   281	13	jubalix
   282	13	jettico
   283	13	jackyrozario
   284	13	d5000
   285	13	cromaclear
   286	13	POPPP
   287	13	Jimmy2011
   288	12	xchrix
   289	12	xadidos
   290	12	sepehr
   291	12	pocesar
   292	12	mww
   293	12	maxbit
   294	12	italovers
   295	12	d13id
   296	12	ROBERTO
   297	12	EpicThomas
   298	12	Coinsy
   299	12	Armando
   300	12	ArcticWolfie
   301	11	rb2
   302	11	qqNxt
   303	11	professorhandsome
   304	11	nesco1805
   305	11	mczarnek
   306	11	matt608
   307	11	feeleep
   308	11	Choboy
   309	11	Agent86
   310	10	grizmoblust
   311	10	barbierir
   312	10	ParmaBTC
   313	10	NWO
   314	10	Krabby
   315	10	Komputor
   316	10	GröBkAz
   317	10	DiCE1904
   318	10	BitCoiner2012
   319	10	96redformula
   320	9	zerocom
   321	9	tillou
   322	9	stdset
   323	9	rdanneskjoldr
   324	9	oldnbold
   325	9	nxtuser
   326	9	nelisky
   327	9	mynxtcoin
   328	9	mudshark79
   329	9	markus1000
   330	9	marcoslopez
   331	9	jelin1984
   332	9	extee
   333	9	dittie
   334	9	cfrm
   335	9	bittick
   336	9	Xtar
   337	9	X68N
   338	9	Tompa
   339	9	Thingamajig
   340	9	ThePatient
   341	9	Nyx
   342	9	Edacra
   343	9	Dps23
   344	9	DeadlyEskimo
   345	8	zakorus
   346	8	ycm82
   347	8	tooroth
   348	8	stereotype
   349	8	puck2
   350	8	nxt-e.com
   351	8	noashh
   352	8	masterOfDisaster
   353	8	hyunsookmom
   354	8	hobbster
   355	8	halabibk
   356	8	drdops
   357	8	demols
   358	8	chinabreak123
   359	8	btcruss
   360	8	asdlolciterquit
   361	8	aorith
   362	8	Xio
   363	8	X_X_X
   364	8	N[e]wBie
   365	8	NXT
   366	8	MtheK
   367	8	Kaliber1
   368	8	Istanbul34
   369	8	HinnomTX
   370	8	Gaman
   371	7	wwdz99
   372	7	wastedbit
   373	7	titan20
   374	7	sussex
   375	7	skytaper
   376	7	shinep
   377	7	rnr
   378	7	maratmmz
   379	7	hoax
   380	7	eXtatiC
   381	7	canuck
   382	7	bitfromit
   383	7	bitbets
   384	7	arafel71
   385	7	alxx77
   386	7	Stark-Fujikawa
   387	7	Snard
   388	7	Kmonk
   389	7	Jaguar0625
   390	7	Jackevin
   391	7	JKBtCn
   392	7	Gonzo418
   393	7	CommanderVenus
   394	7	Boiar
   395	6	subhead
   396	6	spud3861
   397	6	sherrifshenko
   398	6	pilotbo
   399	6	naurisdede
   400	6	mvag
   401	6	mellorbo
   402	6	leetrump
   403	6	jdebunt
   404	6	himmelsfaller2
   405	6	fehen
   406	6	dulinxu
   407	6	dawn
   408	6	cryptohunter
   409	6	cryptobanks
   410	6	bitoktlk
   411	6	bitcool
   412	6	SpeedDemon13
   413	6	Rluner
   414	6	Morguk
   415	6	Ludom
   416	6	Luceat
   417	6	Lubliana
   418	6	JohnDoe21
   419	6	Jcsarokin
   420	6	GroinCoin
   421	6	CryptKeeper
   422	6	BCFrex
   423	5	yesuper
   424	5	xyz
   425	5	vitvert
   426	5	virtualaddict
   427	5	techo051
   428	5	stamen123
   429	5	slothbag
   430	5	shoichikun808
   431	5	scor2k
   432	5	schnib12
   433	5	rmKHT
   434	5	panhc2014
   435	5	ojman28
   436	5	nonstopdonkey
   437	5	neonemu
   438	5	nemra
   439	5	mishan
   440	5	mikaljan
   441	5	jari76
   442	5	hilotime
   443	5	gobpaul
   444	5	dudenohair
   445	5	dave5555
   446	5	crendore
   447	5	coloredcoin
   448	5	caishendizi
   449	5	boredeo
   450	5	axxian
   451	5	alexrussel1980
   452	5	Xandrexx
   453	5	Voodah
   454	5	Sondey10mg
   455	5	Silv0r
   456	5	Orrechorre
   457	5	MrFring
   458	5	LiveFree
   459	5	Fry
   460	5	Fastpow
   461	5	FandangledGizmo
   462	5	Elokane
   463	5	CCInvestor
   464	5	Boing7898
   465	4	wezelvis
   466	4	vgo
   467	4	usafinders
   468	4	td services
   469	4	tadakaluri
   470	4	stoneone
   471	4	standards
   472	4	soho01592
   473	4	slavo
   474	4	simpleunit
   475	4	sava0123
   476	4	rigel
   477	4	rajc
   478	4	podohost
   479	4	lovebit
   480	4	loumatrix
   481	4	larue05
   482	4	kitkat007
   483	4	jenya-les12
   484	4	jchi18
   485	4	hichman
   486	4	furball
   487	4	freedomfighter
   488	4	ewibit
   489	4	esse83
   490	4	dimirfu
   491	4	datguyian
   492	4	cxhjmfl
   493	4	chindit
   494	4	aan
   495	4	User500
   496	4	Trade101
   497	4	TM
   498	4	Sparky_eMunie
   499	4	PiNX
   500	4	Mogly

Definitely missing people. I have at least 50 posts and am not in this list.

[xyzzyx]

the list is actually 1018 lines long, I cut it to only 100, the following is top500:

Code:

   rank npost   id
     1	4541	Come-from-Beyond
   ...
   141	46	lyynx
   ...

Definitely missing people. I have at least 50 posts and am not in this list.

The list is difficult to read since there are so many entries, but you're there.

[CoinTropolis_JustaBitTime]

Austin Bitcoin Conference Prep

Heard back from Michael DeMarco over at Freedomain Radio, he asked us to swing by at the Austin Bitcoin Conference.  Emails going out, hoping to get quite a few responses in the next few days for our team. First introductions always help get the ball rolling before stepping foot into the chaos.

** Update 1 **

Lamar over at Pheeva would like to meet

http://www.wkyt.com/yourtown/locations/lexington/headlines/Pheeva-has-received-rave-reviews-for-new-product-246776381.html


** Update 2 **

The Bitcoin Wife wants to meet with us, she's already familiar with Nxt!


** Update 3 **

Bitcoin100 - Emailing back and forth now

[allwelder]

Once again, someone needs to clarify some things for me. Please correct the following process, it could be total bullshit:

1. James uses AE + AM and three servers to make a gateway for external coins
2. Sending DOGE to the gateway triggers an automated process to send DOGE assets from the Nxt accounts of the servers to the sender's Nxt account
3. Sending DOGE assets back to the gateway triggers the servers to send DOGE coins back to a DOGE address

cannot log into http://nxtra.org/nxt-client/.

[msin]

Suggested NIP (Nxt Improvement Proposal)

Adding "meta information" to Arbitrary Messages.

As AMs are going to become a key communication tool for various other parts of the Nxt system (including NIPs themselves) I suggest that we decide on one of the two ways of providing minimal "meta" information for AMs.

This could be done in the following 2 ways:

1) Encode them as URIs (making it simple for web apps to handle different kinds of things).

or

2) Use the first x bits of the AM to indicate the type.

The advantage of 1 is the simplicity for web apps (i.e. no coding necessary) and the advantage of 2 is size (we only have 1000 bytes for an AM currently).

Which way we go is up to the community - but whichever way I would like to see then an NIP AM (which might just contain the hash of an NIP document - the document itself could be posted on forums or wherever else).

By having such information your "inbox" could automatically place messages in different folders and could also perhaps sound an "alert" according to the AM type received (e.g. we might expect to also have an "alert" AM a bit like Bitcoin alerts).

Great idea, especially since AM will be used as a reputation system in clients soon.

[jl777]

Suggested NIP (Nxt Improvement Proposal)

Adding "meta information" to Arbitrary Messages.

As AMs are going to become a key communication tool for various other parts of the Nxt system (including NIPs themselves) I suggest that we decide on one of the two ways of providing minimal "meta" information for AMs.

This could be done in the following 2 ways:

1) Encode them as URIs (making it simple for web apps to handle different kinds of things).

or

2) Use the first x bits of the AM to indicate the type.

The advantage of 1 is the simplicity for web apps (i.e. no coding necessary) and the advantage of 2 is size (we only have 1000 bytes for an AM currently).

Which way we go is up to the community - but whichever way I would like to see then an NIP AM (which might just contain the hash of an NIP document - the document itself could be posted on forums or wherever else).

By having such information your "inbox" could automatically place messages in different folders and could also perhaps sound an "alert" according to the AM type received (e.g. we might expect to also have an "alert" AM a bit like Bitcoin alerts).

Is there a way to do both? Since URI will be a lot longer than 4 bytes, we could reserve a four byte code that web apps could read, which would mean the URI immediately follows. If it is not the code for URI follows, then the web apps should ignore it. Apps that need to use all the 1000 bytes would be able to filter the AM's that just have their special code.

James

[xyzzyx]

Suggested NIP (Nxt Improvement Proposal)

Adding "meta information" to Arbitrary Messages.
...
1) Encode them as URIs (making it simple for web apps to handle different kinds of things).

or

2) Use the first x bits of the AM to indicate the type.

Is there a way to do both? Since URI will be a lot longer than 4 bytes, we could reserve a four byte code that web apps could read, which would mean the URI immediately follows. It is is not the code for URI follows, then the web apps should ignore it. Apps that need to use all the 1000 bytes would be able to filter the AM's that just have their special code.

Yes.  The suggestion of 7-bit ASCII with a variable length allows the type-tag to be dual-purposed as a URI as long as the string starts with a known URI scheme.

[LemonAndFries]

So I've been having trouble setting up a node under Debian.

This is the error I get after 0.8.3 starts:

./run.sh: line 1:  3004 Killed                  java -Xmx1024M -cp nxt.jar:lib/*:conf nxt.Nxt

Help is appreciated.

did you use apt-get to install java?  give us output from "uname -a" and "which java" and "java -version"

uname: Linux 5inko.2 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2+deb7u2 x86_64 GNU/Linux

which java: /usr/bin/java

java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1~deb7u1)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)

thanks in advanced, need to learn me some more linux.

[xyzzyx]

So I've been having trouble setting up a node under Debian.

This is the error I get after 0.8.3 starts:

./run.sh: line 1:  3004 Killed                  java -Xmx1024M -cp nxt.jar:lib/*:conf nxt.Nxt

Help is appreciated.

did you use apt-get to install java?  give us output from "uname -a" and "which java" and "java -version"

uname: Linux 5inko.2 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2+deb7u2 x86_64 GNU/Linux

which java: /usr/bin/java

java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1~deb7u1)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)

thanks in advanced, need to learn me some more linux.

I'm also using OpenJDK 1.7.0 but on Ubuntu.  How much RAM does your machine have?

[LemonAndFries]

So I've been having trouble setting up a node under Debian.

This is the error I get after 0.8.3 starts:

./run.sh: line 1:  3004 Killed                  java -Xmx1024M -cp nxt.jar:lib/*:conf nxt.Nxt

Help is appreciated.

did you use apt-get to install java?  give us output from "uname -a" and "which java" and "java -version"

uname: Linux 5inko.2 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2+deb7u2 x86_64 GNU/Linux

which java: /usr/bin/java

java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1~deb7u1)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)

thanks in advanced, need to learn me some more linux.

I'm also using OpenJDK 1.7.0 but on Ubuntu.  How much RAM does your machine have?

Well it's not a PC, it's server space I'm renting off DigitalOcean to run a VPS.  It has 512MB RAM.

[jl777]

I have made an internal proposal to the NXTcash team using the latest source code that will allow us to make a release that can be considered for mainnet use. Not sure how long it will take as I will need to start and finish Nodecoin 2.0 to fully implement the proposed NXTcash solution, not to mention a fair amount of work in the client code.

Before you say, "but we can't store the giant zeroknowledge proofs in the NXT blockchain!", let me say that the method I am proposing does not need to store the big proof in the blockchain, just the NXTcash minting and spending events. Still working out all the kinks, but I am optimistic.

<shameless plug>
Show your support for NXTcash, donate to completion bounty fund 13313092584524529006
</shameless plug>

The way I see this working is that from the client you can directly mint new NXTcash, in increments of 100NXT. This will create private files that are encrypted and stored on your computer (and USB backup). Now the files on your USB are just like cash. You can then go to any other computer and launch the NXTcash spending app. You tell it what NXT acct (different one) to fund with the private files on USB.

At this point, we can go in two possible ways, one way is to have the new NXT acct funded with NXT, or it could be NXTcash asset. We are assessing the tradeoffs between the two approaches, but either way, funds have gone from the initial acct to the new account, without any identifiable information being leaked!

What you do with your NXTcash is your business. Anything you do from the alter-ego acct is all publicly viewable, but the key is that nobody can identify who is controlling that new account.

James

[EmoneyRu]

Well it's not a PC, it's server space I'm renting off DigitalOcean to run a VPS.  It has 512MB RAM.

Remove "-Xmx1024M". Don't add any Xmx. For VPS it is the best variant.

Btw, managing node can be automated in 2 ways: (1) (2).

[xyzzyx]

I have made an internal proposal to the NXTcash team using the latest source code that will allow us to make a release that can be considered for mainnet use. Not sure how long it will take as I will need to start and finish Nodecoin 2.0 to fully implement the proposed NXTcash solution, not to mention a fair amount of work in the client code.

Before you say, "but we can't store the giant zeroknowledge proofs in the NXT blockchain!", let me say that the method I am proposing does not need to store the big proof in the blockchain, just the NXTcash minting and spending events. Still working out all the kinks, but I am optimistic.
...

Sounds like you're talking about using another chain for the zero-knowledge proofs and putting the hash (pointer) of the ZK block in the Nxt blockchain via AM, effectively using the PoS of Nxt to secure the second chain, no?

[jl777]

I have made an internal proposal to the NXTcash team using the latest source code that will allow us to make a release that can be considered for mainnet use. Not sure how long it will take as I will need to start and finish Nodecoin 2.0 to fully implement the proposed NXTcash solution, not to mention a fair amount of work in the client code.

Before you say, "but we can't store the giant zeroknowledge proofs in the NXT blockchain!", let me say that the method I am proposing does not need to store the big proof in the blockchain, just the NXTcash minting and spending events. Still working out all the kinks, but I am optimistic.
...

Sounds like you're talking about using another chain for the zero-knowledge proofs and putting the hash (pointer) of the ZK block in the Nxt blockchain via AM, effectively using the PoS of Nxt to secure the second chain, no?

In essence yes, but with some differences. I want to get confirmation from the team that I am not crazy before disclosing more details though

James

[xyzzyx]

I have made an internal proposal to the NXTcash team using the latest source code that will allow us to make a release that can be considered for mainnet use. Not sure how long it will take as I will need to start and finish Nodecoin 2.0 to fully implement the proposed NXTcash solution, not to mention a fair amount of work in the client code.

Before you say, "but we can't store the giant zeroknowledge proofs in the NXT blockchain!", let me say that the method I am proposing does not need to store the big proof in the blockchain, just the NXTcash minting and spending events. Still working out all the kinks, but I am optimistic.
...

Sounds like you're talking about using another chain for the zero-knowledge proofs and putting the hash (pointer) of the ZK block in the Nxt blockchain via AM, effectively using the PoS of Nxt to secure the second chain, no?

In essence yes, but with some differences. I want to get confirmation from the team that I am not crazy before disclosing more details though

James

Cool. Parallel chains, here we come.