Topic: Closed Thread - page 132. (Read 677703 times)
Congrats! Yes, expect many sleepless nights and unproductive days ahead!
Well, now someone has the right to rest 
Just couple of hours ago our dear TheRealSilk became a father. Let's all wish good luck to lucky daughter and her wonderful parents! )))
Ian, we love You! )
G-d bless! ))
Congratulations... and good luck. He will need them both. Just couple of hours ago our dear TheRealSilk became a father. Let's all wish good luck to lucky daughter and her wonderful parents! )))
Ian, we love You! )
G-d bless! ))
Well, now someone has the right to rest
Just couple of hours ago our dear TheRealSilk became a father. Let's all wish good luck to lucky daughter and her wonderful parents! )))
G-d bless! ))
Just couple of hours ago our dear TheRealSilk became a father. Let's all wish good luck to lucky daughter and her wonderful parents! )))
G-d bless! ))
All the best to the new family member and parents !
I think resting is over for them now
Well, now someone has the right to rest
Just couple of hours ago our dear TheRealSilk became a father. Let's all wish good luck to lucky daughter and her wonderful parents! )))
Ian, we love You! )
G-d bless! ))
Just couple of hours ago our dear TheRealSilk became a father. Let's all wish good luck to lucky daughter and her wonderful parents! )))
Ian, we love You! )
G-d bless! ))
Price dropped also 
It's still the same old bug that forces us to restart the main nodes periodically. All transactions is saved, so nothing to worry about. The new client eliminated this bug - but another one, more serious bag has appeared 
We have launched a test network to find the problem (http://nodemoney.com:20000), but staff is on holiday today and TheRealSilk has valid reasons be absent as well
We have launched a test network to find the problem (http://nodemoney.com:20000), but staff is on holiday today and TheRealSilk has valid reasons be absent as well 
yep- last Block:
6347 8/1/2015 05:46:10 1,000.00000 3.50000 411300365913335504
No transactions today from 6:00 a.m.? Which is the last block?
Yep, last block 6347 also in blockexplorer
No transactions today from 6:00 a.m.? Which is the last block?
When approximately there is a new wallet for linux? I want to begin forging.
But in clientConfig.js i have to put the account id or the password?
the password, but obvious attention to account security.
anyway, to forging you need at least 500000 node.
How much are people making off of forging at the moment?
Every wallet with 500,000+ on ballance and enter the network regularly or make a transaction forging money. Today on early beta coins is still inexpensive so "transactions" have greater weight than "time". However, when somebody making transaction to improve its forging weight then somebody else getting comission from that, so the system tends to equilibrium in proportion to increasing the number of users.
Hi to all, i have followed guido for installation of client in vps, it works some hours and after the block suddenly stop of update and i need to restart manually the service (evidently i lost all activity points), i´m using debian 7 64bits vps, the node version is 0.35 and i´m too using the latest linux version of nodecoin,
thank you in advance
thank you in advance
I sent You PM where asked to write more detailed symptoms of the problem.
But in clientConfig.js i have to put the account id or the password?
This is a beta feature that will be corrected.
If you will put password to that file then theoretically if someone will get access to your server he can read it.
It's much safer to enter a passphrase manually so we did not upload it to the main manual.
I think I'm seeing something similar. I have over 1%, forging away, on a node that has been running non-stop for over a week. For a while I was getting about 25% of all blocks. Now, I'vd not seen my account hit a block for days.
My account is the 9689... one. At my heigth of generation, I was getting every other block. Now... Nothing and I'm on a rock-solid system with a good network connection.
Instead of resetting counters, I suggest running statistical averages on each node and provide more blocks for the healthiest nodes. I know changes are coming to the PoA algorithm. I hope this is the approach you take. I would.
Also, if you can derive a good metric to determine the health of a node, the. You can get rid of the need to monitor user balances. Also, I think wouldn't even care if the account is sending/receiving funds. If there is an account on the network, associated with a node that has 99.999% uptime and a dedicated fibre line, it deserves to hit blocks, even if it's balance is 0.
That's just my opinion. Keep up the good work. Thanks devs!
My account is the 9689... one. At my heigth of generation, I was getting every other block. Now... Nothing and I'm on a rock-solid system with a good network connection.
Instead of resetting counters, I suggest running statistical averages on each node and provide more blocks for the healthiest nodes. I know changes are coming to the PoA algorithm. I hope this is the approach you take. I would.
Also, if you can derive a good metric to determine the health of a node, the. You can get rid of the need to monitor user balances. Also, I think wouldn't even care if the account is sending/receiving funds. If there is an account on the network, associated with a node that has 99.999% uptime and a dedicated fibre line, it deserves to hit blocks, even if it's balance is 0.
That's just my opinion. Keep up the good work. Thanks devs!
It's always a pleasure to read your ideas.
Actually, we are constantly trying to improve the algorithm and testing many approaches and ideas but we always have to give preference to universality. Improving of algo and the coefficients will remain even after payment system release, and we will try to make the forging process as open and fair as possible within the universal solution.
But in clientConfig.js i have to put the account id or the password?
the password, but obvious attention to account security.
anyway, to forging you need at least 500000 node.
How much are people making off of forging at the moment?
But in clientConfig.js i have to put the account id or the password?
the password, but obvious attention to account security.
anyway, to forging you need at least 500000 node.
But in clientConfig.js i have to put the account id or the password?
Thanks man
After a few months of 24/7 uptime I am just now beginning to see gains from forging in my account. It seems as if it was not working very well before, but I am now actually accumulating Nodes through the forging process. Good job devs, keep up the good work.
Hi to all, i have followed guido for installation of client in vps, it works some hours and after the block suddenly stop of update and i need to restart manually the service (evidently i lost all activity points), i´m using debian 7 64bits vps, the node version is 0.35 and i´m too using the latest linux version of nodecoin,
thank you in advance
thank you in advance
latest version - 0.9.4.1b
http://nodecoin.com/node_9.4.1b_linux.zip
instructions for linux: https://github.com/nodepay/Docs/blob/master/Instructions.md
Correct me if I'm wrong, but the point of a needing a balance for such things is to (only) mitigate the risk of a SA, is so the cost of such an operation is to expensive to be practical.
No system (that I'm aware of) is 100% protected against the outlier cases of a sybil. I think, you could potentially monitor a few metrics and use them for calculating the value of a node. If a very-healthy node is expensive to maintain (constant uptime, with restarts of servers being very brief, and a fast connection) you can mark the node as a "really good one". If someone wants to cheat the system by creating an array of super-nodes, it should be expensive if the network of people and services using the network is large. Also, if you have a very rigid process for validating blocks and TXs, you could slap heavy penalty "weights" on nodes so that can't forge for a LONG time.
I've been thinking about reputation in a trustless network in the back of my mind for a couple years but for a different type of application. My gut is that there is an alogrithmic "sweet spot" where you can award healthy, but poor, nodes with the ability to mine blocks. I'd have to get out the calculator and fudge some network statistics coz I don't have a massive network to test on, but I think this can be done.
The "problem" with my request is that a simple solution might not be simple to derive. Using a balance as a means to determine who can forge is easy-- just look at a number on an account and then apply a little math to it. However, statistically analyzing a graph-network, distributing consistent (verifiable) results and then deriving a meaningful output is difficult. But, once you've found the magical formula, you're golden.
Sorry for this and my former post. I get ideas and I post them a little faster than I should when I login here BEFORE I get my AM coffee.
😴
No system (that I'm aware of) is 100% protected against the outlier cases of a sybil. I think, you could potentially monitor a few metrics and use them for calculating the value of a node. If a very-healthy node is expensive to maintain (constant uptime, with restarts of servers being very brief, and a fast connection) you can mark the node as a "really good one". If someone wants to cheat the system by creating an array of super-nodes, it should be expensive if the network of people and services using the network is large. Also, if you have a very rigid process for validating blocks and TXs, you could slap heavy penalty "weights" on nodes so that can't forge for a LONG time.
I've been thinking about reputation in a trustless network in the back of my mind for a couple years but for a different type of application. My gut is that there is an alogrithmic "sweet spot" where you can award healthy, but poor, nodes with the ability to mine blocks. I'd have to get out the calculator and fudge some network statistics coz I don't have a massive network to test on, but I think this can be done.
The "problem" with my request is that a simple solution might not be simple to derive. Using a balance as a means to determine who can forge is easy-- just look at a number on an account and then apply a little math to it. However, statistically analyzing a graph-network, distributing consistent (verifiable) results and then deriving a meaningful output is difficult. But, once you've found the magical formula, you're golden.
Sorry for this and my former post. I get ideas and I post them a little faster than I should when I login here BEFORE I get my AM coffee.
😴
Sure it depends on the metrics but not requiring any balance would imho be risky. NEM (shameless plug) actually has a reputation system for nodes (not network wide though, just direct peers). It uses the Eigentrust++ algorithm. It's based on data though and not really on uptime.
Jump to: