I am had thought it would be easy to use AE for crypto gateway, especially considering BCNext's discussion about BTC gateway. It is also important to have NXT Asset 100% backed by actual asset, be it loaf of bread, BTC or turtles.
For anything that isn't all created at genesis, a one time quantity is wrong. Almost all real world things will have a variable number, especially if we have a BTC gateway using AE
right. consider how stocks can split, etc Actually, we should consider this more carefully. Think of the different types of asset markets - consider Anon136's silver bullion asset. Instead of adding qty, maybe since his asset market doesnt depend on ratios and dividends like stocks do of his asset he should just create 1 billion assets and issue them as appropriate; In his case of Assets/markets there is never need to increase QTY. But then we should also implement a new transaction and API for an asset split/reverseSplit, where if the split/reverseSplit transaction is in the blockchain for that particular asset, then the qty of that asset for each holder is halved/doubled. BAM easy-peasey. And Im sure that in the future there may need to be some kind of dividend-NXT-payout API/transaction as well. Are there any other types of markets we should plan for? |
|
|
|
I am had thought it would be easy to use AE for crypto gateway, especially considering BCNext's discussion about BTC gateway. It is also important to have NXT Asset 100% backed by actual asset, be it loaf of bread, BTC or turtles.
For anything that isn't all created at genesis, a one time quantity is wrong. Almost all real world things will have a variable number, especially if we have a BTC gateway using AE
right. consider how stocks can split, etc |
|
|
|
Ive never done anything with jetty web server before - anyone here have experience using SSL certs with the jetty https server? Im using eclipse docs at http://wiki.eclipse.org/Jetty/Howto/Configure_SSL and have used keytool to import the intermediate cert and the purchased cert into my new keystore file where Ive written over the default one in the NRS package with my new one. Also edited jetty-ssl.xml with my OBF:obfuscatedpassword as well as done the same thing for file jetty-spdy-proxy.xml To be honest, not sure if I was just supposed to just change the passwords in those files or add other stuff. The doc mentions adding a call names "addConnector" but when I try to add it as docs suggests as <Call name="addConnector">
<Arg>
<New class="org.eclipse.jetty.server.ssl.SslSelectChannelConnector">
<Arg>
<New class="org.eclipse.jetty.http.ssl.SslContextFactory">
<Set name="keyStore"><SystemProperty name="jetty.home" default="." />/etc/keystore</Set>
<Set name="keyStorePassword">OBF:1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4</Set>
<Set name="keyManagerPassword">OBF:1u2u1wml1z7s1z7a1wnl1u2g</Set>
<Set name="trustStore"><SystemProperty name="jetty.home" default="." />/etc/keystore</Set>
<Set name="trustStorePassword">OBF:1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4</Set>
</New>
</Arg>
<Set name="port">7875</Set>
<Set name="maxIdleTime">30000</Set>
</New>
</Arg>
</Call>
(Using my own obfuscated password in there, not the default in the code above) Then I get java.lang.ClassNotFoundException: org.eclipse.jetty.server.ssl.SslSocketConnector crash on starting the NRS jar file. I also tried using SslSocketConnector instead of SslSelectChannelConnector as docs suggest; same thing. If I leave that addConnector out, 'java -jar start.jar' hangs after reading wellKnownPeers Any help on jetty admins? |
|
|
|
|
wow, so its expected that NXT drops as BTC drops, but doge is rising despite BTCs drop
|
|
|
|
Is it possible to issue fees for the AE? For example if Person A wants to buy 500 Assets and Person A pays 500 NXT for them, will it be possible for me as the asset owner to issue a fee of 5 NXT for this transaction?
afaik no. Basically you can only profit from an asset when you create it, or when you pay dividends (not payout 100%) Okay thanks. hmmm.. but it seems like etherium would let you put the logic for that in there? |
|
|
|
So what are people testing this thing on. Do we have an experimental nrs version out now that lets you issue test assets?
ive CLI'ed the API in a bash script if people dont want to use a 2nd party client. Not that is does not use https due to limitation with curl. so only ever use it on your localhost, except the testnet will be ok since it doesnt use real NXT or real accounts. And Im not 100% sure but I also believe it will only work with numbers/letters for passphrase as some characters hose up in curl # cat /usr/local/sbin/ncli
#!/bin/bash
# to update for additional API calls, enter the new command in the array API, but be sure to
# keep the case switch sections in the same order as in the API array
#
API=(getAccount cancelBidOrder cancelAskOrder getBidOrder getAskOrder getAccountCurrentBidOrderIds getAccountCurrentAskOrderIds getBidOrderIds getAskOrderIds placeBidOrder placeAskOrder transferAsset getAsset getAssetIds issueAsset sendMoney getTransactionBytes getTransaction broadcastTransaction decodeToken getPeers getPeer getAccountId getAccountBlockIds getAccountPublicKey getAccountTransactionIds getBalance getGuaranteedBalance assignAlias getAliasId getAliasIds getAliasURI listAccountAliases sendMessage getBlock getConstants getMyInfo getState getTime decodeHallmark markHost)
if [ "$2" = "l" ]; then
HOST="127.0.0.1"
else
HOST=$2
fi
if [ "$HOST" = "holms.cloudapp.net" ]; then
PORT="6874"
else
PORT="7874"
fi
case "$1" in
getAccount)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&account\=$3\×tamp=$4 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server account timestamp"
fi
;;
cancelBidOrder)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&secretPhrase\=$3\&order\=$4\&fee\=$5\&deadline\=$6 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server passphrase orderID fee deadline"
fi
;;
cancelAskOrder)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&secretPhrase\=$3\&order\=$4\&fee\=$5\&deadline\=$6 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server passphrase orderID fee deadline"
fi
;;
getBidOrder)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&order\=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server orderID"
fi
;;
getAskOrder)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&order\=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server orderID"
fi
;;
getAccountCurrentBidOrderIds)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&account\=$3\&asset\=$4 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server account asset(optional)"
fi
;;
getAccountCurrentAskOrderIds)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&account\=$3\&asset\=$4 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server account asset(optional)"
fi
;;
getBidOrderIds)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&asset\=$3\×tamp\=$4 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server assetID timestamp"
fi
;;
getAskOrderIds)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&asset\=$3\×tamp\=$4 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server assetID timestamp"
fi
;;
placeBidOrder)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&secretPhrase=$3\&asset\=$4\&quantity\=$5\&price\=$6\&fee\=$7\&deadline\=$8 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server passphrase asset quantity price fee deadline "
fi
;;
placeAskOrder)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&secretPhrase=$3\&asset\=$4\&quantity\=$5\&price\=$6\&fee\=$7\&deadline\=$8 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server passphrase asset quantity price fee deadline "
fi
;;
transferAsset)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&secretPhrase=$3\&recipient\=$4\&asset\=$5\&quantity\=$6\&fee\=$7\&deadline\=$8 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server passphrase recipient asset quantity fee deadline "
fi
;;
getAsset)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&asset\=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server assetID "
fi
;;
getAssetIds)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server "
fi
;;
issueAsset)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&secretPhrase\=$3\&name\=$4\&description\=$5\&quantity\=$6\&fee\=$7 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server passphrase name description quantity fee "
fi
;;
sendMoney)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&secretPhrase\=$3\&recipient\=$4\&amount\=$5\&fee=$6\&deadline\=$7 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server passphrase recipient amount fee deadline"
fi
;;
getTransactionBytes)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&transaction\=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server transactionID"
fi
;;
getTransaction)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&transaction\=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server transactionId"
fi
;;
broadcastTransaction)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&transactionBytes\=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server bytecode"
fi
;;
decodeToken)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&website\=$3\&token\=$4 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server site.domain.tld 160characterToken"
fi
;;
getPeers)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server"
fi
;;
getPeer)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&peer\=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server peerIPorDNS"
fi
;;
getAccountId)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&secretPhrase\=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server passphrase"
fi
;;
getAccountBlockIds)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&account\=$3\×tamp\=$4 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server account timestamp"
fi
;;
getAccountPublicKey)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&account\=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server account"
fi
;;
getAccountTransactionIds)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&account\=$3\×tamp\=$4 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server account timestamp"
fi
;;
getBalance)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&account\=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server account"
fi
;;
getGuaranteedBalance)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&account\=$3\&numberOfConfirmations\=$4 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server account numberOfConfirmationsRequired"
fi
;;
assignAlias)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&secretPhrase\=$3\&alias\=$4\&uri\=$5\&fee\=$6\&deadline\=$7 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server passphrase alias uri fee deadline"
fi
;;
getAliasId)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&alias\=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server alias"
fi
;;
getAliasIds)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\×tamp\=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server timestamp"
fi
;;
getAliasURI)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&alias=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server alias"
fi
;;
listAccountAliases)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&account=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server account"
fi
;;
sendMessage)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&secretPhrase\=$3\&recipient\=$4\&fee=$5\&message\=$6\&deadline\=$7 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server passphrase recipient fee HEX deadline"
echo "note the message is NOT sent encrypted. Encrypt yourself if required"
fi
;;
getBlock)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&block=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server blockID"
fi
;;
getConstants)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server"
fi
;;
getMyInfo)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server"
fi
;;
getState)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server"
fi
;;
getTime)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server"
fi
;;
decodeHallmark)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&hallmark=$3 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server hallmarkString"
fi
;;
markHost)
if [[ "$HOST" != "help" && "$HOST" != "" ]]; then
curl -s http://$HOST:$PORT/nxt\?requestType\=$1\&secretPhrase=$3\&host\=$4\&weight\=$5\&date\=$6 | python -m json.tool | sed -e 's/\([]"{}[,]\)//g'
else
echo "ncli $1 server passphrase IPaddressOrDNSname weight date"
echo "where date format is YYYY-MM-DD"
fi
;;
*) echo ""
echo "Usage: ncli APIcmd server option1 option2..."
echo ""
echo "where server is IP/DNS or use l to query localhost"
echo "and options are APIcmd specific"
echo "API commands:"
for item in ${API[*]}
do
printf " %s\n" $item
done
echo "use 'ncli APIcmd help' for more help on a particular API command"
;;
esac
|
|
|
|
Is it possible to issue fees for the AE? For example if Person A wants to buy 500 Assets and Person A pays 500 NXT for them, will it be possible for me as the asset owner to issue a fee of 5 NXT for this transaction?
Could anyone translate this in Russian? It appears that he, as person-A the asset issuer, wants the ability to charge person-B for the privilege of buying any qty of the asset, even when person-A buys from an external party, person-C, simply because person-A is the asset issuer. I cant think why that would be needed. It's not a bug. It's a reassignment.
Perhaps if the alias is found to exist and not have been changed (in terms of the "data" part) then it shouldn't be broadcast as a tx at all? yes, in the very least, clients should implement this |
|
|
|
i have a question about passwords. If you have a weak password your coins will be stolen, because of the rainbowtable guys. But isn't it true that when these rainbow guys try to bruteforce an account. And every time they enter a non-existing passwords then each time a new account is created within next?
So if you create a new account with a weak password you probably access an already created account which was bruteforced earlier. There are ofcourse no coins in these accounts so you think they are new. Is there no way to signal that you are entering an already existing account? So you know that you should not send coins to this 'new' account
if you open in already used account you will see transactions |
|
|
|
|
ok you're gonna have to explain what the differences are between active/passive forging. I do not get how you are making the distinction
|
|
|
|
whatever model we choose - I suggest we try to run it on top of NXT via AM; this architecture is BCNext's actual goal for NXT. CfB has stated he would consult for free for someone attempting this
I guess I need some more info about this AM thing. What is the practical use of this?  Can someone please explain this to a newbie  I have little knowledge of these extra features of NXT... Apparently BCNext's plan all along was to build NXT as an extensible infrastructure, kind of like etherium has been, but for different architectures. In the case of NXT, its AM feature is ideal to use for creating brand new crypto coins. CfB is currently working on one such coin but is delayed and has said he would help someone attempting to do the same. |
|
|
|
Running Nxt over torI tried to run Nxt over tor using torsocks, but apparently this doesn't work for java. The way to tell java to use a socks proxy is to define socksProxyHost and socksProxyPort properties, in a system properties file or on the command line: java -DsocksProxyHost=127.0.0.1 -DsocksProxyPort=9050 -Xmx1024M -jar start.jar
Replace 127.0.0.1 and 9050 with your tor host and socks port, if not default. Basically this is equivalent to the socks proxy options in the configuration of bitcoin-qt, if you use that. You cannot use tor if you want to advertise a public IP or run a bootstrapping node, so only use it on your mining node, if you care about preserving your privacy. And you cannot hallmark a node ran behind tor, so if you are a stakeholder and want to contribute to the network stability, please consider running a separate publicly visible hallmarked node (and if you want to anonymize that one too, need to use a VPN which allows port forwarding and dynamic DNS). this is a bit old, but I have some questions on how NRS works that is applicable to its appropriate use with tor. How does NRS deal with DNS names that it sees in incoming requests, and for DNS names when it wants to create a new connection outbound? These scenarios have nothing to do with hallmarking, so we can safely discard those discussions... Lets first discuss when NRS receives a new connection from an external node: Obviously, the IP packet itself just contains IP addresses, but what does NRS do when the external node's web.xml does not have an IP address in there, but instead has a DNS name? Does the local NRS first query DNS, and then check to see if the IP address returned by DNS matches the IP address in the incoming IP packet? If so, what happens if there is a mismatch? Or does the local NRS simply read the DNS passed over JSON and think to itself "ok IP address X is claiming to be DNS name Y; thats nice, now I will still just use the IP address to respond to the external , regardless of what the DNS really resolves to." The issue here is that if DNS is queried, then most likely the java process is doing this outside the scope of tor, resulting in leaking through your real IP address to DNS servers. ( I say most likely, I use this proxy-type setup with firefox over sshd's dynamic socks proxy, and this by default leaks to DNS; appropriate extra counter-steps must be taken) The same thing would happen for outbound-initiated connections, whether from the seeded wellknownhosts or from learning about the DNS names from other peers - if the local node wants to query DNS before connecting, then real IP address will be leaked. So how does NRS deal with DNS? |
|
|
|
|
i installed tor on my ubuntu system, can someone tell me how to make the NRS java client use tor and not the computer's default gateway?
|
|
|
|
|
whatever model we choose - I suggest we try to run it on top of NXT via AM; this architecture is BCNext's actual goal for NXT. CfB has stated he would consult for free for someone attempting this
|
|
|
|
|
james, just chill man. please. you have lots of good ideas, unfortunately, just as you cannot implement them all yourself, neither can the most of us. I dont know about you guys but NXT is one of my 'hobbies' - they are supposed to be fun. If it gets to the point where its not, then maybe you do need to reevaluate though. chill dude, and try to get some perspective here. yes there is lots to do but there is lots of time. just deal with the decentralized nature of the beast.
|
|
|
|
Here are some suggestions on how to improve over Nxt
(1) Don't let the user choose the passphrase by default. Brain wallet should be an advanced feature and not a default option. Generate a 256-bit random seed for the user, and save that (in encrypted form) in wallet.dat file. The user will provide the password for the encryption. Don't ever save the seed unencrypted on the hard drive, ever. Don't make that an available option. Encryption password must be a requirement (and the user must type it twice).
(2) Make the accounts deterministic, so the user will only have to back up wallet.dat once (not like Bitcoin's QT where regular backups are required).
Basically, it should work something like this:
seed = 256-bit randomly generated and saved encrypted in wallet.dat
Account-One = Hash (seed)
If the user creates more accounts,
Account-two = Hash (Account-One + seed)
Account-three = Hash (Account-two + seed)
etc etc .
The user can create as many accounts as they want. As long as they never lose the seed, they will be fine. No regular backups required.
(3) Do not include any code that has anything to do with signing transaction in server code. The signing should be client's job. That way the users who don't want to download the server software can just download a lightweight client and connect to a public node and safely use it without ever transmitting the secret seed over the internet.
Thanks forweighing in here. Ive already made these suggesions except for the detrministic part. I like it. Im quoting you so jg will be sure to not miss i |
|
|
|
Release 0.7.2
After update to 0.7.2 I ended up now 3 times in a row on a fork with just one block in last 4 days and insane targets, I let it run for about an hour now and it does not seem to be able to recover from that. Me too. I downloaded (almost) the entire chain from vps2.nxtcrypto.org. Could the admin of that node check it's ok? Eithrr thatt vps is on correct chain or all my vps are on fork |
|
|
|
version 0.7.x runs stable for me.
JL , you bring it up to production state, step by step.
Keep up the good work!!!
seems to be pretty stable for me as well. did get this though: [2014-02-08 16:04:55.838] DEBUG: Will pop block 16510352762190493348 at height 61626
[2014-02-08 17:16:06.707] DEBUG: Will pop block 13029646756006985243 at height 61676
[2014-02-08 18:31:33.122] DEBUG: Failed to analyze hallmark for peer nxt.homer.ru, java.nio.BufferUnderflowException
|
|
|
|
Do we have a thread for those who deserve Dev Bounties from unclaimed Nxt? I recommend the following allocation for dev:
QBTC (nxtcrypto) - 100k
Passion_LTC (Nxtvote, Nxtion, etc) - 150k
l8oore (asset exchange) - 200k
We can add to these amounts in the future for ongoing projects.
Also, should I even bother with the crypto algo review? Sounds like Jesse James can help us with that. On that note I recommend a 250k bounty for Jesse James from unclaimed dev Nxt. If we still want a crypto review, I can use 10 BTC from my own wallet, but I need a very clear and concise response on what we specifically need from someone reviewing the algo.
very generous thank you msin! Pin, can you start a poll for sending unclaimed Nxt to the people above? is the asset exchange up and running now? should that one wait? |
|
|
|
|
Please critique my security strategy:
1. ubuntu OS on 8GB RAM laptop
2. comment out swap entry in fstab
3. fstab has a tmpfs RAMdrive mounted on boot
4. use onetime to generate an encrypted file on the RAMdrv where key is same length as passphrase
5. move that encrypted file to disk for local storage, USB, cloud, family, friends, etc for safekeeping
6. bonus: make OTP key such that an easily-memorized misspell generates a different passphrase that belongs to other account that has history. PLAUSIBLE DENIABILITY
|
|
|
|
|
ok ill go ahead and ask the question, what does "Failed to accept block received from X, blacklisting" mean? What if it is a peer that I have very good reason to suspect is not evil?
|
|
|
|
|
Show Posts
