Closed Thread

[patmast3r]

Please can someone explain how exactly NODE forging works? I have a NODE that will run constantly. So I can optimize the forging block sending NODEs to other people?
But it is necessary to wait a while between one transaction and another? How long is the wait?
THX!

Sure, this is how it works:

At the moment there are 2 primordial parameters that define which node is going to be elected: Time & Spent Volume(ammount)!

at the beginning when the forging module will be set in place: your timeHeight(the amount of time that you spent online since your last connection) will be calculated by the network and compared to other nodes timeHeight.

After determining the time, the second parameter will kick in and will determine the spent amount since your last login, each node will value 1unit of time - adding an extra second for each node you sent out of your account.

Those will be summed acordingly and we'll get the Nodeheight = timeHeight + Units

Practical example:
blockgeneration time: 14:00 pm 21/09/14
Node I(icharles123) connected @ 1:00 pm  21/09/14 and hasn't made any transaction => timeHeight=3600s + 0 Units = 3600NodeHeight
Node A (Mr.hotdog) connected @ 1:05 pm  21/09/14 and sent 1 node.  => timeHeight=2700s + 1 Unit = 2701 NodeHeight

Nodeheight 3600 > Nodeheight 2701 =>  Node I > Node A => Node I will generate the block!

After a block is generated Node I's NodeHeight will be reseted, and the cycle will restart!


Questions?

Yes and the whitepaper unfortunately doesn't address this.
How you prevent me from looping my NODEs through a couple of accounts boosting my Nodeheight through the amount of "spent" NODEs ? Is there any magic going on or is it "just" the fees ?

[1714800870]

1714800870

[1714800870]

1714800870

[1714800870]

1714800870

[1714800870]

1714800870

[danzilla]

Please can someone explain how exactly NODE forging works? I have a NODE that will run constantly. So I can optimize the forging block sending NODEs to other people?
But it is necessary to wait a while between one transaction and another? How long is the wait?
THX!

Sure, this is how it works:

At the moment there are 2 primordial parameters that define which node is going to be elected: Time & Spent Volume(ammount)!

at the beginning when the forging module will be set in place: your timeHeight(the amount of time that you spent online since your last connection) will be calculated by the network and compared to other nodes timeHeight.

After determining the time, the second parameter will kick in and will determine the spent amount since your last login, each node will value 1unit of time - adding an extra second for each node you sent out of your account.

Those will be summed acordingly and we'll get the Nodeheight = timeHeight + Units

Practical example:
blockgeneration time: 14:00 pm 21/09/14
Node I(icharles123) connected @ 1:00 pm  21/09/14 and hasn't made any transaction => timeHeight=3600s + 0 Units = 3600NodeHeight
Node A (Mr.hotdog) connected @ 1:05 pm  21/09/14 and sent 1 node.  => timeHeight=2700s + 1 Unit = 2701 NodeHeight

Nodeheight 3600 > Nodeheight 2701 =>  Node I > Node A => Node I will generate the block!

After a block is generated Node I's NodeHeight will be reseted, and the cycle will restart!


Questions?

Yes and the whitepaper unfortunately doesn't address this.
How you prevent me from looping my NODEs through a couple of accounts boosting my Nodeheight through the amount of "spent" NODEs ? Is there any magic going on or is it "just" the fees ?

After you generate a block, it looks like the NodeHeight is reset, so anyone online longer than you will have an advantage.  But if you send many many Nodes, and there are not a lot of people who have been online for a long time, maybe you would be the one to generate a block?

Since timeHeight is in seconds, and 1 node is the equivalent of 1 second, you would need to send 86400 nodes to be equal to another node that has been online for 24 hours and sent nothing (24*60*60).  Maybe the "time value" of each node should be lower at the start until there is enough use and value, like 10 nodes per second or something?  What do you guys think.

[patmast3r]

Please can someone explain how exactly NODE forging works? I have a NODE that will run constantly. So I can optimize the forging block sending NODEs to other people?
But it is necessary to wait a while between one transaction and another? How long is the wait?
THX!

Sure, this is how it works:

At the moment there are 2 primordial parameters that define which node is going to be elected: Time & Spent Volume(ammount)!

at the beginning when the forging module will be set in place: your timeHeight(the amount of time that you spent online since your last connection) will be calculated by the network and compared to other nodes timeHeight.

After determining the time, the second parameter will kick in and will determine the spent amount since your last login, each node will value 1unit of time - adding an extra second for each node you sent out of your account.

Those will be summed acordingly and we'll get the Nodeheight = timeHeight + Units

Practical example:
blockgeneration time: 14:00 pm 21/09/14
Node I(icharles123) connected @ 1:00 pm  21/09/14 and hasn't made any transaction => timeHeight=3600s + 0 Units = 3600NodeHeight
Node A (Mr.hotdog) connected @ 1:05 pm  21/09/14 and sent 1 node.  => timeHeight=2700s + 1 Unit = 2701 NodeHeight

Nodeheight 3600 > Nodeheight 2701 =>  Node I > Node A => Node I will generate the block!

After a block is generated Node I's NodeHeight will be reseted, and the cycle will restart!


Questions?

Yes and the whitepaper unfortunately doesn't address this.
How you prevent me from looping my NODEs through a couple of accounts boosting my Nodeheight through the amount of "spent" NODEs ? Is there any magic going on or is it "just" the fees ?

After you generate a block, it looks like the NodeHeight is reset, so anyone online longer than you will have an advantage.  But if you send many many Nodes, and there are not a lot of people who have been online for a long time, maybe you would be the one to generate a block?

Since timeHeight is in seconds, and 1 node is the equivalent of 1 second, you would need to send 86400 nodes to be equal to another node that has been online for 24 hours and sent nothing (24*60*60).  Maybe the "time value" of each node should be lower at the start until there is enough use and value, like 10 nodes per second or something?  What do you guys think.

What If I'm constantly online (still no idea how that is even verified unless I fail to generate block when it's my turn) AND send NODES around like a maniac ?

The fees are probably high enough to make this very expensive I'm just wondering if there is another mechanism at play to avoid this.

[danzilla]

Please can someone explain how exactly NODE forging works? I have a NODE that will run constantly. So I can optimize the forging block sending NODEs to other people?
But it is necessary to wait a while between one transaction and another? How long is the wait?
THX!

Sure, this is how it works:

At the moment there are 2 primordial parameters that define which node is going to be elected: Time & Spent Volume(ammount)!

at the beginning when the forging module will be set in place: your timeHeight(the amount of time that you spent online since your last connection) will be calculated by the network and compared to other nodes timeHeight.

After determining the time, the second parameter will kick in and will determine the spent amount since your last login, each node will value 1unit of time - adding an extra second for each node you sent out of your account.

Those will be summed acordingly and we'll get the Nodeheight = timeHeight + Units

Practical example:
blockgeneration time: 14:00 pm 21/09/14
Node I(icharles123) connected @ 1:00 pm  21/09/14 and hasn't made any transaction => timeHeight=3600s + 0 Units = 3600NodeHeight
Node A (Mr.hotdog) connected @ 1:05 pm  21/09/14 and sent 1 node.  => timeHeight=2700s + 1 Unit = 2701 NodeHeight

Nodeheight 3600 > Nodeheight 2701 =>  Node I > Node A => Node I will generate the block!

After a block is generated Node I's NodeHeight will be reseted, and the cycle will restart!


Questions?

Yes and the whitepaper unfortunately doesn't address this.
How you prevent me from looping my NODEs through a couple of accounts boosting my Nodeheight through the amount of "spent" NODEs ? Is there any magic going on or is it "just" the fees ?

After you generate a block, it looks like the NodeHeight is reset, so anyone online longer than you will have an advantage.  But if you send many many Nodes, and there are not a lot of people who have been online for a long time, maybe you would be the one to generate a block?

Since timeHeight is in seconds, and 1 node is the equivalent of 1 second, you would need to send 86400 nodes to be equal to another node that has been online for 24 hours and sent nothing (24*60*60).  Maybe the "time value" of each node should be lower at the start until there is enough use and value, like 10 nodes per second or something?  What do you guys think.

What If I'm constantly online (still no idea how that is even verified unless I fail to generate block when it's my turn) AND send NODES around like a maniac ?

The fees are probably high enough to make this very expensive I'm just wondering if there is another mechanism at play to avoid this.

Yeah we can hear more from the dev about it soon, I'm sure.  But my understanding is that every time you generate a block, your time resets to zero, so other people who have not generated a block have an advantage.  The time starts counting when you first sign in, and resets if you sign out or generate a block.

[HunterMinerCrafter]

Wish there was REP on this board. I enjoy your posts. Breath of fresh air on this cesspool site. Checking out the Zen thread now.

I totally agree. Constructive posts like HunterMinerCrafter's are always welcome. Even posts critical of Node are certainly welcome, provided you actually provide some valid points that give people something to discuss and possibly improve upon.

"Me smell scam", "Dev abandoned coin", and "Are we on Bittrex yet? Are we on Bittrex yet?" unfortunately do not qualify

Thanks!  It means a lot to me to have the support of people like the both of you.

It seems that the newbie accounts (and particularly some newbie devs accounts!) often are either misunderstanding or dismissive of the things I try to bring to the table.  Sometimes they just don't want to hear it or, in some cases, don't even want it said at all, I suspect.

It is good to know that the message does get through to, at least, those willing and able to receive it!

[Hueristic]

Wish there was REP on this board. I enjoy your posts. Breath of fresh air on this cesspool site. Checking out the Zen thread now.

I totally agree. Constructive posts like HunterMinerCrafter's are always welcome. Even posts critical of Node are certainly welcome, provided you actually provide some valid points that give people something to discuss and possibly improve upon.

"Me smell scam", "Dev abandoned coin", and "Are we on Bittrex yet? Are we on Bittrex yet?" unfortunately do not qualify

...or, in some cases, don't even want it said at all, I suspect....

QFT

[evergrow]

NODE can't run on my Macbook, right?

[lukey25]

NODE can't run on my Macbook, right?

there's no wallet for mac, yet

[Depredation]

Lots of sell resistance at 120-130 sat, and lots of buy resistance at 90

[lukey25]

Lots of sell resistance at 120-130 sat, and lots of buy resistance at 90

price seems stable now

[evergrow]

NODE can't run on my Macbook, right?

there's no wallet for mac, yet

Will there be one in the future? And if so, when (ETA)?

Cheers!

[Hueristic]

NODE can't run on my Macbook, right?

VM?

[hypersire]

NODE can't run on my Macbook, right?

If you only have a Macbook, your best bet is to download VirtualBox (free) and then you can run both Linux and Windows VMs. Of course Linux ISOs are free, as for Windows, I'm sure you know where you can pick up a copy of that for free as well 

[evergrow]

NODE can't run on my Macbook, right?

If you only have a Macbook, your best bet is to download VirtualBox (free) and then you can run both Linux and Windows VMs. Of course Linux ISOs are free, as for Windows, I'm sure you know where you can pick up a copy of that for free as well  

Thanks bud, but I don't want to use Windows. I was asking what the ETA is for the real Mac client.

I would either need a standalone Mac or Linux client  Is there an ETA for that already? I'm having my coins on BTER right now

[3x2]

NODE can't run on my Macbook, right?

If you only have a Macbook, your best bet is to download VirtualBox (free) and then you can run both Linux and Windows VMs. Of course Linux ISOs are free, as for Windows, I'm sure you know where you can pick up a copy of that for free as well  

Thanks bud, but I don't want to use Windows. I was asking what the ETA is for the real Mac client.

I would either need a standalone Mac or Linux client  Is there an ETA for that already? I'm having my coins on BTER right now

you can you use online wallet to generate your wallet address and then simply send them there. your password is your account so use a stronger password.

[whitecloud]

Why gets windows client always connected only to 5.45.124.65 and 5.45.114.108... this is what I see under 'Peers'?

Thx

For windows client peers do not show, it will be available in later versions
On the Linux everything is fine

Tonight will be a new version client

Where can I download the linux version? The linux symbol on first page is not linked...

Next week will be linux version

[schnidl]

I wont unlock my wallet until there is a mac version. is this a problem? will i loose my stake if it seems like i'm not active?

[HunterMinerCrafter]

...or, in some cases, don't even want it said at all, I suspect....

QFT

Sad, isn't it?

Even more sad that so many people so readily "buy right into it."

[hypersire]

NODE can't run on my Macbook, right?

If you only have a Macbook, your best bet is to download VirtualBox (free) and then you can run both Linux and Windows VMs. Of course Linux ISOs are free, as for Windows, I'm sure you know where you can pick up a copy of that for free as well  

Thanks bud, but I don't want to use Windows. I was asking what the ETA is for the real Mac client.

I would either need a standalone Mac or Linux client  Is there an ETA for that already? I'm having my coins on BTER right now

I can totally understand that, I haven't used Windows as my main OS since Red Hat Linux 5.2 came out back in '98-'99

However, back when I only had a Macbook I felt I had no choice but to run a Windows VM because I was missing out on too many opportunities since the Windows wallet is usually the priority for devs.

Anyway, it sounds like the Linux and Mac wallets will be ready soon so no worries, just use BTER or the online wallet until then.

[lcharles123]

Please can someone explain how exactly NODE forging works? I have a NODE that will run constantly. So I can optimize the forging block sending NODEs to other people?
But it is necessary to wait a while between one transaction and another? How long is the wait?
THX!

Sure, this is how it works:

At the moment there are 2 primordial parameters that define which node is going to be elected: Time & Spent Volume(ammount)!

at the beginning when the forging module will be set in place: your timeHeight(the amount of time that you spent online since your last connection) will be calculated by the network and compared to other nodes timeHeight.

After determining the time, the second parameter will kick in and will determine the spent amount since your last login, each node will value 1unit of time - adding an extra second for each node you sent out of your account.

Those will be summed acordingly and we'll get the Nodeheight = timeHeight + Units

Practical example:
blockgeneration time: 14:00 pm 21/09/14
Node I(icharles123) connected @ 1:00 pm  21/09/14 and hasn't made any transaction => timeHeight=3600s + 0 Units = 3600NodeHeight
Node A (Mr.hotdog) connected @ 1:05 pm  21/09/14 and sent 1 node.  => timeHeight=2700s + 1 Unit = 2701 NodeHeight

Nodeheight 3600 > Nodeheight 2701 =>  Node I > Node A => Node I will generate the block!

After a block is generated Node I's NodeHeight will be reseted, and the cycle will restart!


Questions?

Yes and the whitepaper unfortunately doesn't address this.
How you prevent me from looping my NODEs through a couple of accounts boosting my Nodeheight through the amount of "spent" NODEs ? Is there any magic going on or is it "just" the fees ?

After you generate a block, it looks like the NodeHeight is reset, so anyone online longer than you will have an advantage.  But if you send many many Nodes, and there are not a lot of people who have been online for a long time, maybe you would be the one to generate a block?

Since timeHeight is in seconds, and 1 node is the equivalent of 1 second, you would need to send 86400 nodes to be equal to another node that has been online for 24 hours and sent nothing (24*60*60).  Maybe the "time value" of each node should be lower at the start until there is enough use and value, like 10 nodes per second or something?  What do you guys think.

What If I'm constantly online (still no idea how that is even verified unless I fail to generate block when it's my turn) AND send NODES around like a maniac ?

The fees are probably high enough to make this very expensive I'm just wondering if there is another mechanism at play to avoid this.

Yeah we can hear more from the dev about it soon, I'm sure.  But my understanding is that every time you generate a block, your time resets to zero, so other people who have not generated a block have an advantage.  The time starts counting when you first sign in, and resets if you sign out or generate a block.

So it works like a queue? If someone generate the block, only the Nodeheight of him resets and gives place to the next queued in the ranking? Interesting!

To count the seconds we need to keep the logged in account or just let the program running?