Search content
Sort by
Showing 20 of 149 results by intel
I have created a new thread to discuss how to use the Asset Exchange legally.
Please join and share yout thoughts:
https://bitcointalk.org/index.php?topic=460377
Please join and share yout thoughts:
https://bitcointalk.org/index.php?topic=460377
Please share you thoughts about this topic.
It is nice to have this functionality, but if we can´t figure out a way how to use the money made with AE, then all these efforts in createding a running AE are worthless.
Anon beat you to the punch by a few minutes I think... there's an AE thread going on here:
https://bitcointalk.org/index.php?topic=460343
I was thinking about discussing the opportunities hoe to get the money out of the AE legally. I know someone who owns a comapyn in Austria and would love to use the AE to fund one of the projects of the company, but he is affraid that this would be illegal money. And as of now, I can´t tell him that it isn´t. So this thread should focus on the legal issues around AE.
Making legal money into illegal is very simple nowadays, huh?
ANNOUNCEMENT:
nxtFreeRider is available at:
www.quicknxt.com/FreeRider
sha256: 0b04c63911c877ba8dfb88bed1618c63590eeeb82cec42263c0452082f21402d nxtFreeRider01.zip
please note: in terms of User Experience, this is an extremely rough release. However, the implementation of the API backend is complete, robust and multithreaded. The intention is to release a fully open sourced pythonic API, that can be directly inspected and extended by anybody capable of writing python code.
Screenshoots?
I hope NXT Asset Exchange 'll not have a hole which XCP have.
Anyone can place an order which is not backed by any deposited instrument:
http://www.blockscan.com/order_book.aspx (somebody please do the screenshot).
The issue discussion is here: https://forums.counterparty.co/index.php/topic,69.0.html
Anyone can place an order which is not backed by any deposited instrument:
http://www.blockscan.com/order_book.aspx (somebody please do the screenshot).
The issue discussion is here: https://forums.counterparty.co/index.php/topic,69.0.html
You? Of course you should not. It's designed for people thinking about secure messaging.
For secure messages I can use OTR for free.
Your IP 'll not be hidden. If you are journalist in Sochi who is using public jabber with OTR, you 'll be arrested for spreading true stories anyway
You just dont understand what it means - secure IM.
Why should I pay anything for messages if I can chat @ fb? Messages should be used for technical staff and should be well-paid. 1.0
You? Of course you should not. It's designed for people thinking about secure messaging.
$10 USD per 1 NXT is very pessimistic price for the end of 2014.
are you guys on crack or something - I really do not want to be a pessmist but why on earth should there be a 10b market cap for nxt in the end of 2014?
Dont also be confused with 10b cap, you 'll never get 10b when trying to sell all the NXT.
$10 USD per 1 NXT is very pessimistic price for the end of 2014.
are you guys on crack or something - I really do not want to be a pessmist but why on earth should there be a 10b market cap for nxt in the end of 2014?
Because even stupid forks costs more with absolutely no background. NXT has features which you may not fully understand yet, but bitcoin is nothing against them.
$10 USD per 1 NXT is very pessimistic price for the end of 2014.
So, if we 'll have 0.01 NXT fee per transaction, it means 1 transaction 'll cost $0.10 which looks valid for most of merchants and NXT users.
We should decide, is it 0.01 or 0.001. Let me remind that only because of small fee (with many zero in the number) bitcoin costs now 800-1000 USD per each. It was not possible with 0.1 or 0.01 BTC fee per operation (100 USD or 10 USD per operation).
I vote for 0.001 fee. We must be realists and be ready for mass adoption usage scenario which fortunately/unfortunately increase the price of NXT. Also we cant change the fee every week or so - it's crazy.
Community, you decide the fee for years, not for few months!
Welcome to 0.001 Club!
PS: 0.001 Club Members 'll get ability to use P2P encrypted messaging service (via NXT AM) and pay almost nothing for secure communication of next generation!
PPS: 0.001 Club Members 'll increase their equity value of NXT, guaranteed.
So, if we 'll have 0.01 NXT fee per transaction, it means 1 transaction 'll cost $0.10 which looks valid for most of merchants and NXT users.
We should decide, is it 0.01 or 0.001. Let me remind that only because of small fee (with many zero in the number) bitcoin costs now 800-1000 USD per each. It was not possible with 0.1 or 0.01 BTC fee per operation (100 USD or 10 USD per operation).
I vote for 0.001 fee. We must be realists and be ready for mass adoption usage scenario which fortunately/unfortunately increase the price of NXT. Also we cant change the fee every week or so - it's crazy.
Community, you decide the fee for years, not for few months!
Welcome to 0.001 Club!
PS: 0.001 Club Members 'll get ability to use P2P encrypted messaging service (via NXT AM) and pay almost nothing for secure communication of next generation!
PPS: 0.001 Club Members 'll increase their equity value of NXT, guaranteed.
Before spending any money on advertising, please fix this:
It's the quote written by some random guy on other forum.
Quote
Well I hope Its more easy than next client which is the most complicated thing I ever saw
I installed it but dont see any wallet only an account number on a web page ! with some sort of secret phrase to unlock
Tried the faucet but seen no coins coming but the whole thing is not for an average guy ( must create a bat file and hopefully someone on the forum next made a translation but it still remain totally unclear
I installed it but dont see any wallet only an account number on a web page ! with some sort of secret phrase to unlock
Tried the faucet but seen no coins coming but the whole thing is not for an average guy ( must create a bat file and hopefully someone on the forum next made a translation but it still remain totally unclear
It's the quote written by some random guy on other forum.
Two screenshots of what I've been busy with for my NXT Solaris client. To be released over the weekend, since I need a rest.
Market view
Personal account management showing NXT values in other currencies
Be careful with the market view, though. You know, it's closed source and I might have something in there that influences the markets in the direction I want...
Market view
Personal account management showing NXT values in other currencies
Be careful with the market view, though. You know, it's closed source and I might have something in there that influences the markets in the direction I want...
Is the program connects to your server to grab some tick history to build a graph?
Important announcement
BCNext devised a way to handover unclaimed coins in such a way that doesn't require multisig and still keeps the spirit of decentralization.
BCNext will choose 10 people. I'll contact these people privately to ask for an account id. Each of them will create a special account and send it to me. 1M NXT will be sent to each account (10M total, not 9M, so the community is supposed to subsidize the public nodes by itself). Jean-Luc will be asked to add a special code that blocks outgoing transactions from these special accounts. When the community decides how to spend part of the unclaimed coins, Jean-Luc will change the code to allow partial withdrawals possible. 10 chosen ones will send 1/10th of the required amount to the account the funds r supposed to go to.
Notes: Only account ids will be published, names of the people who control them will be known only to BCNext and me. Jean-Luc won't be included into this group. The goal of this obscurity is to remove community pressure on the chosen ones.
Discuss, the community may put veto on this approach.
BCNext devised a way to handover unclaimed coins in such a way that doesn't require multisig and still keeps the spirit of decentralization.
BCNext will choose 10 people. I'll contact these people privately to ask for an account id. Each of them will create a special account and send it to me. 1M NXT will be sent to each account (10M total, not 9M, so the community is supposed to subsidize the public nodes by itself). Jean-Luc will be asked to add a special code that blocks outgoing transactions from these special accounts. When the community decides how to spend part of the unclaimed coins, Jean-Luc will change the code to allow partial withdrawals possible. 10 chosen ones will send 1/10th of the required amount to the account the funds r supposed to go to.
Notes: Only account ids will be published, names of the people who control them will be known only to BCNext and me. Jean-Luc won't be included into this group. The goal of this obscurity is to remove community pressure on the chosen ones.
Discuss, the community may put veto on this approach.
Bad idea. REALLY BAD IDEA to change the client software and hard-define transaction rules inside the client. Am i alone who think so?
Yes, that's what I am saying. If, by lowering fees, we see a large increase in transactions, then it will be worth it to lower fees. The question is, will we see that large of an increase right now? If not, then it may be too early to do so.
That's my point we won;t see large transaction increases because someone is not gonna waste 1 Nxt just to send a simple msg.
the cheaper it is for the user the more they will use the service.....period.
Exactly my point, too.
Also, people like to communicate.
They love to send people chatter.
Give them the ability to do so, and I bet you that transactions will take off.
And Nxt is about transactions.
There is a feature that is usuable, so make it easy and cheap to use.
That's all I am saying.
Community should vote using the ... oh wait...
I am for putting it to a vote. The poll will run for 1 week on both Nextcoin & Nxtcrypto.org forums.
I can organize the polls on both forums.
POLL QUESTION: SHOULD WE LOWER TRANSACTION FEE TO 0.01 Nxt?
Yes!
Lol. This must be the most unprofessional move ever.
I can't belive what i just read.
I can't belive what i just read.
+1
I'd prefer sticking with curve25519 for messages.
The public keys are already in the protocol, so you don't need to transamit new ones, it's save, it's easy because you have all the dependencies already there, and it fits the problem perfectly...
The public keys are already in the protocol, so you don't need to transamit new ones, it's save, it's easy because you have all the dependencies already there, and it fits the problem perfectly...
I'd like to remind that each session should use a unique key-pair to avoid known-plaintext attacks.
This is not trival task, sending a public key every time over the network for every message should be enough protected against MITM + protection against PRIVACY LOOKUP ANALYSIS (PROFILING) + many other things.
Jus got this. Browser's UI hanged. Now let's see, if this 'll be self-recovered or not..
Quote
at java.lang.Thread.run(Thread.java:744)
Caused by:
java.lang.InterruptedException
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterrupti bly(AbstractQueuedSynchronizer.java:996)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibl y(AbstractQueuedSynchronizer.java:1303)
at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
at org.eclipse.jetty.util.BlockingCallback.block(BlockingCallback.java:94)
at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:392)
at java.io.FilterOutputStream.write(FilterOutputStream.java:77)
at Nxt$CountingOutputStream.write(Unknown Source)
at java.io.FilterOutputStream.write(FilterOutputStream.java:125)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:282)
at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:125)
at java.io.OutputStreamWriter.write(OutputStreamWriter.java:207)
at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:129)
at java.io.BufferedWriter.write(BufferedWriter.java:199)
at java.io.Writer.write(Writer.java:127)
at Nxt$Block$1.writeJSONString(Unknown Source)
at org.json.simple.JSONValue.writeJSONString(JSONValue.java:135)
at org.json.simple.JSONArray.writeJSONString(JSONArray.java:53)
at org.json.simple.JSONArray.writeJSONString(JSONArray.java:59)
at org.json.simple.JSONValue.writeJSONString(JSONValue.java:135)
at org.json.simple.JSONObject.writeJSONString(JSONObject.java:67)
at org.json.simple.JSONObject.writeJSONString(JSONObject.java:73)
at Nxt.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1568)
at org.eclipse.jetty.servlets.DoSFilter.doFilterChain(DoSFilter.java:457)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:326)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:299)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1539)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:524)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:568)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1110)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:453)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1044)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:199)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:459)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:280)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:229)
at org.eclipse.jetty.io.AbstractConnection$1.run(AbstractConnection.java:505)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536)
at java.lang.Thread.run(Thread.java:744)
[2014-01-11 11:14:41.338] Generated an incorrect block. Waiting for the next one...
[2014-01-11 11:14:47.360] Generated an incorrect block. Waiting for the next one...
[2014-01-11 11:14:49.386] Generated an incorrect block. Waiting for the next one...
[2014-01-11 11:14:51.406] Generated an incorrect block. Waiting for the next one...
[2014-01-11 11:14:51.418] Generated an incorrect block. Waiting for the next one...
[2014-01-11 11:14:51.429] Generated an incorrect block. Waiting for the next one...
[2014-01-11 11:18:17.178] Re-scanning blockchain...
Caused by:
java.lang.InterruptedException
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterrupti bly(AbstractQueuedSynchronizer.java:996)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibl y(AbstractQueuedSynchronizer.java:1303)
at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
at org.eclipse.jetty.util.BlockingCallback.block(BlockingCallback.java:94)
at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:392)
at java.io.FilterOutputStream.write(FilterOutputStream.java:77)
at Nxt$CountingOutputStream.write(Unknown Source)
at java.io.FilterOutputStream.write(FilterOutputStream.java:125)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:282)
at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:125)
at java.io.OutputStreamWriter.write(OutputStreamWriter.java:207)
at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:129)
at java.io.BufferedWriter.write(BufferedWriter.java:199)
at java.io.Writer.write(Writer.java:127)
at Nxt$Block$1.writeJSONString(Unknown Source)
at org.json.simple.JSONValue.writeJSONString(JSONValue.java:135)
at org.json.simple.JSONArray.writeJSONString(JSONArray.java:53)
at org.json.simple.JSONArray.writeJSONString(JSONArray.java:59)
at org.json.simple.JSONValue.writeJSONString(JSONValue.java:135)
at org.json.simple.JSONObject.writeJSONString(JSONObject.java:67)
at org.json.simple.JSONObject.writeJSONString(JSONObject.java:73)
at Nxt.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1568)
at org.eclipse.jetty.servlets.DoSFilter.doFilterChain(DoSFilter.java:457)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:326)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:299)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1539)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:524)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:568)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1110)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:453)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1044)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:199)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:459)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:280)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:229)
at org.eclipse.jetty.io.AbstractConnection$1.run(AbstractConnection.java:505)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536)
at java.lang.Thread.run(Thread.java:744)
[2014-01-11 11:14:41.338] Generated an incorrect block. Waiting for the next one...
[2014-01-11 11:14:47.360] Generated an incorrect block. Waiting for the next one...
[2014-01-11 11:14:49.386] Generated an incorrect block. Waiting for the next one...
[2014-01-11 11:14:51.406] Generated an incorrect block. Waiting for the next one...
[2014-01-11 11:14:51.418] Generated an incorrect block. Waiting for the next one...
[2014-01-11 11:14:51.429] Generated an incorrect block. Waiting for the next one...
[2014-01-11 11:18:17.178] Re-scanning blockchain...
I was asked what an encryption algo should be used in Arbitrary Messages. It's up to u. But u could use https://nextcoin.org/index.php/topic,727.0.html, it's quite simple.
What's current encryption method of AM ? Exactly as written here? https://nextcoin.org/index.php/topic,727.0.html
--- cut ---
I submitted it to more sites, but it is fantastic they really published it
(donations of course welcomed
)PS: I also tweeted to some crypto - celebrities or journalists
Donated. Everybody should do this also.