Author

Topic: NXT :: descendant of Bitcoin - Updated Information - page 2012. (Read 2761645 times)

legendary
Activity: 2142
Merit: 1010
Newbie
If some people rush orders at the same time, the users who in the slow node network will never succeed?

Decentralized exchange isn't suitable for High-frequency trading.
hero member
Activity: 910
Merit: 1000
I don't get it. What's important for accounts who have zero outgoing transactions?
legendary
Activity: 2142
Merit: 1010
Newbie

I have already set the timeout to 10000. Now it's very strange that so many errors during the start of the process, and also error shows up when go to https://localhost:7875

U may deleted "<" or ">" by accident.
legendary
Activity: 2142
Merit: 1010
Newbie
How come  https://localhost:7875/nxt?requestType=getAccountPublicKey&account=  is returning a publicKey even though I have only sent NXT to a specific account?  Should I still send the 1 NXT?

It doesn't matter where u send coins to.
legendary
Activity: 2184
Merit: 1000
Here's the google chrome version of the extension:

http://nxtra.org/alias/NxtAliasSystemChrome.zip

Once downloaded, go to chrome://extensions in your browser, unzip the download, and drag the .crx to your browser page. It should install. I will later add it to the chrome extension directory.

You will have to type "nxt searchterm" in your browser URL bar instead of nxt:searchterm due to differences in browsers.

so Nxtgoogle....is little bit easier than typing Nxt:google
hero member
Activity: 644
Merit: 500
and just focus on the forging part.
Not so good focus though. They're (critics) missing most important details.
sr. member
Activity: 308
Merit: 250
Here's the google chrome version of the extension:

http://nxtra.org/alias/NxtAliasSystemChrome.zip

Once downloaded, go to chrome://extensions in your browser, unzip the download, and drag the .crx to your browser page. It should install. I will later add it to the chrome extension directory.

You will have to type "nxt searchterm" in your browser URL bar instead of nxt:searchterm due to differences in browsers.
full member
Activity: 121
Merit: 100
CFB,

A question, When I signed up a few aliases, I found that sometimes unsuccessful or delayed.

If the future of p2p trade, the deals will be delayed or unsuccessful too? Not real-time and quickly?

Depends on fee and how fast me implement all aspects of Transparent Forging (I mean ability to send transactions directly to next forging node).


If some people rush orders at the same time, the users who in the slow node network will never succeed?
full member
Activity: 168
Merit: 100
IDEX - LIVE Real-time DEX

1. create an aliases with the uri: "acct:YOURACCOUNTNUMBERHERE@nxt"
2. wait a little bit for propagation
3. check http://22k.io/YOURALIAS


When I created my alias for my main account, I left the uri blank.  How do I change it now?

Assign it again with the new URI and 1 nxt fee.
full member
Activity: 238
Merit: 100

I have already set the timeout to 10000. Now it's very strange that so many errors during the start of the process, and also error shows up when go to https://localhost:7875

It ran OK last night in this laptop.

Code:
2013-12-30 23:48:06.339:INFO:oejs.Server:main: jetty-9.1.0.v20131115
2013-12-30 23:48:06.356:INFO:oejdp.ScanningAppProvider:main: Deployment monitor
[file:/C:/nxt/webapps/] at interval 0
2013-12-30 23:48:06.472:WARN:oejx.XmlParser:main: FATAL@null line:60 col:31 : or
g.xml.sax.SAXParseException; lineNumber: 60; columnNumber: 31; 元素类型 "param-n
a??me" 必须由匹配的结束标记 "" 终止。
2013-12-30 23:48:06.474:WARN:oejw.WebAppContext:main: Failed startup of context
o.e.j.w.WebAppContext@13e39a7c{/,file:/C:/nxt/webapps/root/,null}{C:\nxt\webapps
\root}
org.xml.sax.SAXParseException; lineNumber: 60; columnNumber: 31; 元素类型 "param
-na??me" 必须由匹配的结束标记 "" 终止。
        at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAX
ParseException(Unknown Source)
        at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalErro
r(Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(U
nknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
l.scanEndElement(Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
l$FragmentContentDriver.next(Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(U
nknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next
(Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
l.scanDocument(Unknown Source)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
nknown Source)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
nknown Source)
        at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown So
urce)
        at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Un
known Source)
        at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.p
arse(Unknown Source)
        at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(Unknown S
ource)
        at org.eclipse.jetty.xml.XmlParser.parse(XmlParser.java:246)
        at org.eclipse.jetty.webapp.Descriptor.parse(Descriptor.java:65)
        at org.eclipse.jetty.webapp.WebDescriptor.parse(WebDescriptor.java:148)
        at org.eclipse.jetty.webapp.MetaData.setWebXml(MetaData.java:172)
        at org.eclipse.jetty.webapp.WebXmlConfiguration.preConfigure(WebXmlConfi
guration.java:60)
        at org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.jav
a:454)
        at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:490
)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLife
Cycle.java:69)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLi
feCycle.java:117)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.addBean(Container
LifeCycle.java:281)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.addBean(Container
LifeCycle.java:213)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.updateBeans(Conta
inerLifeCycle.java:763)
        at org.eclipse.jetty.server.handler.HandlerCollection.setHandlers(Handle
rCollection.java:89)
        at org.eclipse.jetty.server.handler.ContextHandlerCollection.setHandlers
(ContextHandlerCollection.java:144)
        at org.eclipse.jetty.server.handler.HandlerCollection.addHandler(Handler
Collection.java:155)
        at org.eclipse.jetty.deploy.bindings.StandardDeployer.processBinding(Sta
ndardDeployer.java:41)
        at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:1
86)
        at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentM
anager.java:495)
        at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.j
ava:146)
        at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(Scan
ningAppProvider.java:175)
        at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(Sc
anningAppProvider.java:64)
        at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:605)
        at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:528)
        at org.eclipse.jetty.util.Scanner.scan(Scanner.java:391)
        at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLife
Cycle.java:69)
        at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(Scanni
ngAppProvider.java:145)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLife
Cycle.java:69)
        at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(Deploymen
tManager.java:557)
        at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.
java:232)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLife
Cycle.java:69)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLi
feCycle.java:117)
        at org.eclipse.jetty.server.Server.start(Server.java:355)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(Container
LifeCycle.java:99)
        at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHand
ler.java:60)
        at org.eclipse.jetty.server.Server.doStart(Server.java:324)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLife
Cycle.java:69)
        at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:12
50)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:117
4)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.eclipse.jetty.start.Main.invokeMain(Main.java:297)
        at org.eclipse.jetty.start.Main.start(Main.java:706)
        at org.eclipse.jetty.start.Main.main(Main.java:103)
2013-12-30 23:48:06.508:INFO:oejs.ServerConnector:main: Started ServerConnector@
523e2446{HTTP/1.1}{0.0.0.0:7874}
2013-12-30 23:48:06.759:INFO:oejs.ServerConnector:main: Started ServerConnector@
3d985fe{SSL-http/1.1}{0.0.0.0:7875}

Code:
HTTP ERROR: 503

Problem accessing /. Reason:

    Service Unavailable
Powered by Jetty://
full member
Activity: 196
Merit: 100

1. create an aliases with the uri: "acct:YOURACCOUNTNUMBERHERE@nxt"
2. wait a little bit for propagation
3. check http://22k.io/YOURALIAS


When I created my alias for my main account, I left the uri blank.  How do I change it now?
legendary
Activity: 2142
Merit: 1010
Newbie
That account has no a public key assigned to it yet. To protect urself just send 1 transaction back to ur own account. This will assign a public key and make it impossible to pick the key.

Only accounts that have zero transactions need to do that, right?

Yes, zero outcoming transactions. Later a new type of a transaction will be implemented to assign a public key in advance.
hero member
Activity: 784
Merit: 501
Or perhaps the first 14 digits are 0's is that what you mean?
Exactly.
legendary
Activity: 2142
Merit: 1010
Newbie

Hi yuriygeorge. I was worrying that u had been hit by bus...
hero member
Activity: 750
Merit: 500
www.coinschedule.com
How can an account be 100000 (6 digits)? There's no passphrase you could put in the client to generate an account with so few characters.
You can. If you're lucky enough. Very lucky.

But if

Quote
Passphrase can be any 100 unicode chars
SHA256(passphrase) gives privateKey of 256 bits
Curve25519(privatekey) gives publicKey of 256 bits
SHA256(publickey) gives accountId of 256 bits
First 64 bits of accountId  is 20 digits visibleID (visible in the upper left of the client)

Are you saying that you could have an accountId with just 6 digits? Or perhaps the first 14 digits are 0's is that what you mean?
legendary
Activity: 2142
Merit: 1010
Newbie
What's the story with this? Where can I find more info? How can an account be 100000 (6 digits)? There's no passphrase you could put in the client to generate an account with so few characters.

Someone just made a mistake sending a payment. I believe in 10 years someone will be able to get a key that opens that account.

Edit: I foresee a company that will create computing cluster solely to pick the key. Any ASIC producer could do that.

so how do we protect against this?

That account has no a public key assigned to it yet. To protect urself just send 1 transaction back to ur own account. This will assign a public key and make it impossible to pick the key.
sr. member
Activity: 262
Merit: 250
I hate my family

[via google spreadsheets as of yesterday 12/29]

Redistribution continues, buyers pulling back:

[order book snapshot via google spreadsheets as of today 12/30]
full member
Activity: 168
Merit: 100
IDEX - LIVE Real-time DEX
For those with the restart blues...

If you're using supervisor to manage NRS...

1. Create /etc/cron.hourly/nrs containing:
Code:
#!/bin/bash
supervisorctl restart nrs

2. Make sure it's executable:
Code:
$ sudo chmod +x /etc/cron.hourly/nrs

3. Sit back and relax.
legendary
Activity: 2184
Merit: 1000
What's the story with this? Where can I find more info? How can an account be 100000 (6 digits)? There's no passphrase you could put in the client to generate an account with so few characters.

Someone just made a mistake sending a payment. I believe in 10 years someone will be able to get a key that opens that account.

Edit: I foresee a company that will create computing cluster solely to pick the key. Any ASIC producer could do that.

so how do we protect against this?
member
Activity: 98
Merit: 10
Criticise what I'm suggesting, but first understand my position. Ask questions. Don't assume.

You thought about security only after found several strange 1 NXT incoming transactions. Fear made you to move and speak with community.

Would you like to fund fully completed bounties, which may be interested to you?

Just create a new bounty then, it can be for example - "Security Research of NXT account in forging status", which 'll lead some real specialist to make some really complicated analysis for you and community.

Fund and develop bounties you need, or create a bounty to look and manage good bounties for you.
Jump to: