 Show Posts
|
|
Pages: [1] 2 »
|
|
Wallet does not start in Windows XP 32bit. On Win7 64 is OK.
Registered.
|
|
|
|
|
I rented the rig for 48 hours. Rig was not available about 4 hour, the owner extended the rent time for 5 hours.
Good service. Thanks.
|
|
|
|
is there a byte limit for an alias?
Alias - (0, 100] URI - [0, 1000] NRS if(aliasValue.length() != 0 && aliasValue.length() <= 100) {
alias = aliasValue.toLowerCase();
for(i = 0; i < alias.length() && "0123456789abcdefghijklmnopqrstuvwxyz".indexOf(alias.charAt(i)) >= 0; ++i) {;}
if(i != alias.length()) {
responses.put("errorCode", Integer.valueOf(4));
responses.put("errorDescription", "Incorrect \"alias\" (must contain only digits and latin letters)");
} else {
uri = uri.trim();
if(uri.length() > 1000) {
responses.put("errorCode", Integer.valueOf(4));
responses.put("errorDescription", "Incorrect \"uri\" (length must be not longer than 1000 characters)");
} else {
...
} else {
responses.put("errorCode", Integer.valueOf(4));
responses.put("errorDescription", "Incorrect \"alias\" (length must be in [1..100] range)");
}
|
|
|
|
1. I could add asset filter.
2. Total number of tokens.
3. U can't, u r supposed to emulate matching algo and reconstructs trades according to order placement. I can add extra API calls if necessary.
Strange as for me. Maybe I do not understand how it should work and what does it. I figured it was something like an auction. Ok, I'll look for a more detailed description. |
|
|
|
Come-from-Beyond1. How i can get all orders for specific asset in the one query? I get all orders and do filter it by assetId now. Is there a better way? 2. What is quantity in issue asset request (174 in first row upper table)? 3. I bought a few items. How can I see what I bought and for how much? 
|
|
|
|
How i can get all orders for specific asset in the one query? I can use: do filter ids and run but it is very complicated way. |
|
|
|
Torrent files are around 9kb.
I mitigated the limit by...
It is the wrong way to store .torrent to the blockchain using aliases or AM. I have some .torrent files with size 500KB-1MB. Do you should use one thousand messages for one file? The better way in current stage is using the Magnet-URI. |
|
|
|
|
Whether there is any sense in the generation of an empty (without transactions) block?
|
|
|
|
I counted the number of transactions (83556) and did a little more. Number of accounts is 14600. Full version: charts for transactions, amounts, fees, aliases, accounts. Some charts has logarithmic x scale. All charts: http://imgur.com/Uajg1U4Transactions only:  |
|
|
|
|
Come-from-Beyond
I have questions about the code sometimes. Which topic is better suited to these questions?
Why the "getBaseTarget" is recalculated each time for the same (last) block? For simplicity?
How can I determine that I am in the wrong chain?
Why peers that send a lot of wrong transactions are not stored in the blacklist automatically?
I can send many not verified transactions to each peer and every time they process their (through POST and GET for public which brodcast them to some other peers).
|
|
|
|
Thanks! I found this place: Each time a node sees a transaction it checks if it's the first time a public key used.
If yes, then soft remembers this key, so next user with the same account id will get all transactions rejected.
//Transaction.verify()
else if (account.publicKey == null) {
account.publicKey = senderPublicKey;
} else if (!Arrays.equals(senderPublicKey, account.publicKey)) {
|
|
|
|
64-bit encryption is only used for accounts that have no public key and haven't done any transactions. It is recommended to make public key and do at least one transaction. Send someone some NXT, buy an alias, basically I think any proactive usage of the account gives 256 bit protection
Can anyone explain this in more detail? Or maybe it has already been discussed somewhere. How the presence of a transaction affect the strength of encription? And encription for what? Account ID is hash of public key which is function of private key (secret phrase). Curve25519.keygen(publicKey, null, MessageDigest.getInstance("SHA-256").digest(secretPhrase.getBytes("UTF-8")));
//publicKey - output
byte[] publicKeyHash = MessageDigest.getInstance("SHA-256").digest(publicKey);
BigInteger bigInteger = new BigInteger(1, new byte[]{publicKeyHash[7], publicKeyHash[6], publicKeyHash[5],
publicKeyHash[4], publicKeyHash[3], publicKeyHash[2], publicKeyHash[1], publicKeyHash[0]});
//bigInteger - is account id
If you don't have Transaction you don't have stored Account ID in NRS "database". But how does it affect the existence of the account (as pair the private key-public id)? |
|
|
|
Come-from-BeyondI understand correctly that the public key can not be used to encrypt messages, and private - to decrypt? And i must use another channel for deliver key(s) for message encryption/decryption? First (?) client with arbitrary messaging support. Just for test. QR code generating & scanning for alias, account, payment request included. 
|
|
|
|
|
Jaguar0625
I ran js.core & java.core for a same hash key - the result is different.
You can use java ScriptEngine for mix java & javascript code for testing.
|
|
|
|
The first one created the alias, the second one replaced destination.
James
Thanks! I did not know that the replacement works, I thought this feature is not yet implemented. Petition the maker of your NXT client to add a time check to prevent this from happening in the future.
It's Firefox fault. Not mine or my app  . |
|
|
|
Normal. You can replace an alias URI with a new URI, even if it is the same URI. I consider it a bug, but CfB says it is a feature
James
Maybe i can't understand you properly, but i talk about two same aliases. First is "lr127" (URI is "id:11017826896") and second is "lr127" (same URI "id:11017826896"). I wanted to buy one alias and spend 1 NXT, not 2. But when i query: http://node1.nxtbase.com:7874/nxt?requestType=listAccountAliases&account=11017826896I see only one alias "lr127". As expected. |
|
|
|
|
Come-from-Beyond
Where is aliases? In getTransaction as example.
In version NRS 0.4.7 they exists.
|
|
|
|
But if it's impossible at the protocol level, then maybe we can look at safeguards at the client level. Maybe clients can (at least have the option of) enforcing check digits for entering naked addresses.
NRS API can be changed without breaking backward compatibility. Inside can be stored without check digit - as before. And take / give out only with check digit. NRS & clients must check this, not client only. First time to use the old and new version of account number together, developers need time to change their apps. |
|
|
|
|
