for my forging client running well now, about 16 blocks forged in a bit more than a day. around ~4.7 Crypti
|
|
|
what is going on, block time increased to 3 minutes, and after that to 4 minutes.
|
|
|
woot, forged my first crypti ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) 0.073 in a block ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif) about my 20th block forged
|
|
|
Sorry for disrupting your flame wars ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) , but What is your absolutly most favourite thing about cripti? What you value the most? thanx for me, it is the way crypti handles forging, it is a brilliant system that does what is needs to do(keep up the network, reward purchases, and promote merchants) but is very simple at the same time.
|
|
|
Windows 1 click wallet with easy forging is absolute must.
I'm doing small admin panel for forgers now, wait ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) awesome ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) , looking forward to 0.1.6
|
|
|
will you also extend the wallet API, or is this part of the blockchain explorer?
|
|
|
Yes you must wait for the Node to fully synchronized before trying to launch the wallet in your browser... If you trying to launch the wallet before it is fully synchronized it will cause the Node to restart the sync process... So either monitor your Log or just wait 20 mins to launch the wallet in your browser.. To monitor your Node logs Run this command you could also use tail -f logs.log to see a real time updating view of the logfile in the console, ctrl+c to stop it
|
|
|
gives me a no such file or directory error, opening it in browser gives me a access denied xml error
Please try again. Thanks, it is working now
|
|
|
gives me a no such file or directory error, opening it in browser gives me a access denied xml error
hmmmm, I pulled it down less than 4 hours ago. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FKeYQ13O.png&t=665&c=xGC3WGHOxIILlA) Not sure what's going on with that. I'm not part of the dev team. Maybe GreXX, SyRenity or crypti can tell ya. informer mmh, wierd, running 0.1.5 again now
|
|
|
gives me a no such file or directory error, opening it in browser gives me a access denied xml error
|
|
|
where is the download link to 0.1.5b ? may be stupid but i cant find it on 0.1.5 not b i got the issue where the client reports that i forged all blocks.
|
|
|
the 0.1.5 update works well, forged 5 blocks now with 19 hours of uptime, all empty blocks though ![Sad](https://bitcointalk.org/Smileys/default/sad.gif)
|
|
|
hey, what is the difference between 0.1.5 and 0.1.5b?
|
|
|
Network can receive only one forging request from each IP, so it's not effective to forge with multi accounts from one server.
ah, expected it to be possible if the clients were running on different ports. is it possible if the client are running on the same machine, but on different proxy servers?
|
|
|
hey, why is the blockchain file generated in the parent folder of the folder the client itself is in?
It's obfuscation/minimization problem. ah, thanks for the explanation, btw, is it possible to run several clients on the same blockchain, i'm running all my clients that are forging of different blockchains now, this is not a problem as long as the blockchain is about 10 mb, but will maybe become a problem later on.
|
|
|
hey, why is the blockchain file generated in the parent folder of the folder the client itself is in?
|
|
|
wallet.crypti.me seems to be bugged, blockchain gives the same forging adress for all blocks
|
|
|
setup my node in lubuntu vitrual machine(virtualbox), and it is giving me these errors
{"level":"info","message":"Processing new block...","timestamp":"2014-08-22T22:09:13.404Z"} {"level":"error","message":"Invalid payload length: 7764446715420389358 length: 842 buffer length: 730","timestamp":"2014-08-22T22:09:13.404Z"} {"level":"info","message":"Crypti stopped!","timestamp":"2014-08-22T22:09:13.404Z"} {"level":"error","message":"Error: Can't process block: 7764446715420389358","timestamp":"2014-08-22T22:09:13.404Z"} {"level":"warn","message":"Can't forge, node not synchronized!","timestamp":"2014-08-22T22:09:13.528Z"} {"level":"warn","message":"Can't forge, node not synchronized!","timestamp":"2014-08-22T22:09:14.529Z"} {"level":"warn","message":"Can't forge, node not synchronized!","timestamp":"2014-08-22T22:09:15.530Z"} {"level":"warn","message":"Can't forge, node not synchronized!","timestamp":"2014-08-22T22:09:16.531Z"}
Do you use 0.1.3 version? yeah complete log:http://pastebin.com/eWsDFz81
|
|
|
|