abuelau
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:32:13 PM |
|
More precisely, the account public key becomes known to the blockchain when the first outgoing transaction has been sent from this account. And you can't make an outgoing transaction unless there are funds in the account. So there is some chicken and egg problem here, the very first time you open an account and want to fund it, the above request will tell you that the account is unknown. Client developers should still allow sending money to such an account, but just give a warning. Btw, account # 100000 is still waiting for someone with a supercomputer to get the jackpot... ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) 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.
|
|
|
|
ferment
Full Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 168
Merit: 100
IDEX - LIVE Real-time DEX
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:33:34 PM |
|
I created a nxt alias ( nxtbc) and you can use 22k. http://22k.io/nxtbc
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1010
Newbie
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:34:53 PM |
|
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).
|
|
|
|
utopianfuture
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 602
Merit: 268
Internet of Value
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:35:13 PM |
|
Thought I'd try to find out how my little laptop in the English Countryside sees the network of NXT Nodes After a bit of tinkering I got this... Shows total number of nodes registered to IPs in a particular country and where the IP has a registered geographical location. https://mapsengine.google.com/map/viewer?mid=zDbwNrja6dlY.kwTCMrAWqtAQQuite a geographical spread - but my no means complete I'm sure as I'll only see some of the nodes, probably need files from a few other nodes to get the complete picture unless every node has a complete list - anyone?? Shame I can't query nodes for information otherwise it could be a really interesting picture :/ Ian Ok... now I am about to start getting NXTmotional with all you wonderful people!!! ![Embarrassed](https://bitcointalk.org/Smileys/default/embarrassed.gif) Very interesting.
|
|
|
|
ImmortAlex
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:37:52 PM |
|
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.
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1010
Newbie
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:37:58 PM |
|
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.
|
|
|
|
Damelon
Legendary
Offline
Activity: 1092
Merit: 1010
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:38:30 PM |
|
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. I think I'll just enter a lottery ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
intel
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 98
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:38:39 PM |
|
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.
|
|
|
|
landomata
Legendary
Offline
Activity: 2184
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:40:14 PM |
|
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?
|
|
|
|
ferment
Full Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 168
Merit: 100
IDEX - LIVE Real-time DEX
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:41:13 PM Last edit: December 30, 2013, 04:27:38 PM by ferment |
|
For those with the restart blues... If you're using supervisor to manage NRS... 1. Create /etc/cron.hourly/nrs containing: #!/bin/bash supervisorctl restart nrs
2. Make sure it's executable: $ sudo chmod +x /etc/cron.hourly/nrs
3. Sit back and relax.
|
|
|
|
yuriygeorge
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 262
Merit: 250
I hate my family
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:41:55 PM |
|
![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FE3QJ1l3.png&t=665&c=YXdVQnYugu8EGA) [via google spreadsheets as of yesterday 12/29] Redistribution continues, buyers pulling back: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FD8zqjht.png&t=665&c=7h3jN42bd6qq1Q) [order book snapshot via google spreadsheets as of today 12/30]
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1010
Newbie
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:43:16 PM |
|
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.
|
|
|
|
abuelau
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:43:39 PM |
|
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 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?
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1010
Newbie
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:44:28 PM |
|
Hi yuriygeorge. I was worrying that u had been hit by bus...
|
|
|
|
ImmortAlex
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:46:02 PM |
|
Or perhaps the first 14 digits are 0's is that what you mean? Exactly.
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1010
Newbie
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:47:08 PM |
|
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.
|
|
|
|
rickyjames
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:47:47 PM |
|
1. create an aliases with the uri: "acct:YOURACCOUNTNUMBERHERE@nxt" 2. wait a little bit for propagation 3. check http://22k.io/YOURALIASWhen I created my alias for my main account, I left the uri blank. How do I change it now?
|
|
|
|
NxtChoice
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:51:18 PM |
|
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:7875It ran OK last night in this laptop. 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" 必须由匹配的结束标记 "</param-na??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" 必须由匹配的结束标记 "</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}
HTTP ERROR: 503
Problem accessing /. Reason:
Service Unavailable Powered by Jetty://
|
|
|
|
ferment
Full Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 168
Merit: 100
IDEX - LIVE Real-time DEX
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:52:24 PM |
|
1. create an aliases with the uri: "acct:YOURACCOUNTNUMBERHERE@nxt" 2. wait a little bit for propagation 3. check http://22k.io/YOURALIASWhen 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.
|
|
|
|
coolfish
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 03:54:20 PM |
|
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?
|
Nxt:17482068461146780755
|
|
|
|