[XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 83.

MalReynolds

legendary

Activity: 938

Merit: 1000

Quote from: Litoshi on May 18, 2015, 04:05:20 PM

Quote from: MalReynolds on May 18, 2015, 02:51:25 PM

...Network Monitor... shows 134 computers running 0.2.0a and 6 running 0.2.0 for 140 connected peers. Of these, 2 are Apple, 66 are Windows and 71 are Ubuntu.

...Delegate Monitor...shows 116 total Delegates, with 101 Top Delegates updating the blockchain and 15 other Delegates on standby.

Mal, I would suspect that some of the Delegates are running on Windows Server hosts. You are right, when we update to a Linux only Delegate, the Windows Server clients will either have to run old delegate versions, or go dark. They will then be lacking some functions.

Or they can go Ubuntu on a 0.3.0 upgrade. Do you think they are all running Windows on server farms, or could some of them be on a home ISP? THAT would be interesting...

Say, an aside: I saw Mad Max this weekend, because I am an original fan of that movie franchise from the early 1980s. Run, do not walk, to go see this film. On a scale of 1 to 10 it is a 37. An absolute masterpiece of film making, and I am not alone in that assessment. An astounding 98% of the critic reviews have been enthusiastically positive:

http://www.rottentomatoes.com/m/mad_max_fury_road/reviews/

I will be seeing MM:FR again, just so I can try to focus more on what I only glimpsed in the background the first time around. The background detail in every frame is incredible, and you only get a glimpse before it's on to the next scene. This thing has an average of 22 scene / viewpoint cuts per minute (somebody counted); the action is practically nonstop for two solid hours. You come out feeling like your adrenal glands have been squeezed dry. I actually had tears in my eyes when the credits started to roll.

Litoshi

hero member

Activity: 700

Merit: 500

Member of the Crypti Foundation Board of Directors

Quote from: MalReynolds on May 18, 2015, 02:51:25 PM

Let's talk for a little bit about the Network Monitor here:

http://cryptichain.me/networkMonitor

This currently shows 134 computers running 0.2.0a and 6 running 0.2.0 for 140 connected peers. Of these, 2 are Apple, 66 are Windows and 71 are Ubuntu.

Now let's look at Delegate Monitor here:

http://cryptichain.me/delegateMonitor

This currently shows 116 total Delegates, with 101 Top Delegates updating the blockchain and 15 other Delegates on standby.

Questions:

Are all top delegates shown in the Network Monitor?

If so, how can you tell which are Top Delegates and which are Standby Delegates and which are Crypti Lite nodes?

Since there's 101 Top Delegates and only 71 Ubuntu peers, does that imply that some of the Top Delegates are running Windows / Apple?

If so, what's gonna happen to them when the 0.3.0 release strips forging / delegates out of the Windows code?

Mal, I would suspect that some of the Delegates are running on Windows Server hosts. You are right, when we update to a Linux only Delegate, the Windows Server clients will either have to run old delegate versions, or go dark. They will then be lacking some functions.

Litoshi

hero member

Activity: 700

Merit: 500

Member of the Crypti Foundation Board of Directors

Quote from: stormia on May 18, 2015, 03:43:09 PM

Does Crypti have a Slack group? I really like Slack, it's a great way to interact with the devs and other investors in real time.

We use Slack to communicate internally. We dont have a public channel right now. It has been discussed. Once we made a special channel to talk to 5000bitcoins, who tried to get us to partner with SuperNET......... for like 4 hours!!

One problem with communicating on SLack public channel, is that not all of the community will see the conversation. As you know, we are very responsive to the community, and value their input....... well, not counting starik69 anyway. Mal has good points, and they deserve to be read by the community. A Slack channel would see like a private or exclusive group.

BUT........ If enough of the community wants this..... it can be done.

Vagnavs

legendary

Activity: 1121

Merit: 1003

Quote from: stormia on May 18, 2015, 03:43:09 PM

Does Crypti have a Slack group? I really like Slack, it's a great way to interact with the devs and other investors in real time.

No not to my knowledge.

stormia

hero member

Activity: 868

Merit: 1000

Does Crypti have a Slack group? I really like Slack, it's a great way to interact with the devs and other investors in real time.

MalReynolds

legendary

Activity: 938

Merit: 1000

Let's talk for a little bit about the Network Monitor here:

http://cryptichain.me/networkMonitor

This currently shows 134 computers running 0.2.0a and 6 running 0.2.0 for 140 connected peers. Of these, 2 are Apple, 66 are Windows and 71 are Ubuntu.

Now let's look at Delegate Monitor here:

http://cryptichain.me/delegateMonitor

This currently shows 116 total Delegates, with 101 Top Delegates updating the blockchain and 15 other Delegates on standby.

Questions:

Are all top delegates shown in the Network Monitor?

If so, how can you tell which are Top Delegates and which are Standby Delegates and which are Crypti Lite nodes?

Since there's 101 Top Delegates and only 71 Ubuntu peers, does that imply that some of the Top Delegates are running Windows / Apple?

If so, what's gonna happen to them when the 0.3.0 release strips forging / delegates out of the Windows code?

GreXX

hero member

Activity: 518

Merit: 500

Quote from: Vagnavs on May 17, 2015, 05:34:09 PM

Quote from: Passion_ltc on May 16, 2015, 05:53:15 AM

Crypti Forum now uses HTTPS

Today I want to announce something about this forum. It is now available via HTTPS, which makes it secure against man-in-the-middle attacks.

We recommend you, to always use the HTTPS link to this forum.

https://forum.crypti.me/

If you encounter any problems, please write us!

Okay great. We need some life in this thread and coin. Not much activity lately, hopefully when improvements are done. Things will pick up.
Regards,
Brian

We are all very busy working for the upcoming release, building out first Dapp, and working on a couple key partnerships. You've been with us a long time, just a little bit longer.

Vagnavs

legendary

Activity: 1121

Merit: 1003

Quote from: Passion_ltc on May 16, 2015, 05:53:15 AM

Crypti Forum now uses HTTPS

Today I want to announce something about this forum. It is now available via HTTPS, which makes it secure against man-in-the-middle attacks.

We recommend you, to always use the HTTPS link to this forum.

https://forum.crypti.me/

If you encounter any problems, please write us!

Okay great. We need some life in this thread and coin. Not much activity lately, hopefully when improvements are done. Things will pick up.
Regards,
Brian

Passion_ltc

hero member

Activity: 714

Merit: 500

Crypti Community Manager

Crypti Forum now uses HTTPS

Today I want to announce something about this forum. It is now available via HTTPS, which makes it secure against man-in-the-middle attacks.

We recommend you, to always use the HTTPS link to this forum.

https://forum.crypti.me/

If you encounter any problems, please write us!

crypti

hero member

Activity: 511

Merit: 500

Boris, Crypti Lead Developer, Lisk Advisor

Quote from: MalReynolds on May 15, 2015, 10:31:55 AM

Quote from: dzarmush on May 15, 2015, 08:24:34 AM

How do I check if I forge any blocks at the moment? My LA Vultr node started working worse and worse, so I deleted it and deployed the one in NY/NJ location instead of it, but as I see my uptime is keeping falling. Forging is enabled.

UPD: I checked my delegate through the web wallet, it showed that I wasn't forging. Will try to restart the server.

UPD2: It worked, my delegate is back online.

I had some problems with my Delegate at Vultr, too, and had to do a restart - see below. Middle pix shows crash, bottom pix shows back to current nominal ops.

Anybody have any ideas what happened here or how to prevent it in the future?

We have seen some problems, looks like it memory leaks or something like this.
Please, send me your logs in PM. It will help us to fix it.

Thanks.

MalReynolds

legendary

Activity: 938

Merit: 1000

Quote from: dzarmush on May 15, 2015, 08:24:34 AM

How do I check if I forge any blocks at the moment? My LA Vultr node started working worse and worse, so I deleted it and deployed the one in NY/NJ location instead of it, but as I see my uptime is keeping falling. Forging is enabled.

UPD: I checked my delegate through the web wallet, it showed that I wasn't forging. Will try to restart the server.

UPD2: It worked, my delegate is back online.

I had some problems with my Delegate at Vultr, too, and had to do a restart - see below. Middle pix shows crash, bottom pix shows back to current nominal ops.

Anybody have any ideas what happened here or how to prevent it in the future?

Litoshi

hero member

Activity: 700

Merit: 500

Member of the Crypti Foundation Board of Directors

Quote from: dzarmush on May 15, 2015, 09:02:38 AM

Quote from: Litoshi on May 15, 2015, 08:56:26 AM

Quote from: dzarmush on May 15, 2015, 08:24:34 AM

How do I check if I forge any blocks at the moment? My LA Vultr node started working worse and worse, so I deleted it and deployed the one in NY/NJ location instead of it, but as I see my uptime is keeping falling. Forging is enabled.

UPD: I checked my delegate through the web wallet, it showed that I wasn't forging. Will try to restart the server.

UPD2: It worked, my delegate is back online.

you can watch the Delegate monitor here and see when your Delegte is forging.

http://cryptichain.me/delegateMonitor

I know Delegate Monitor, but I don't see where I can check whether I'm forging or not.

Top of the page.... watch for your delegate to show up in the "last block by"

Clicking on a delegate name will show you the total XCR forged by that delegate

In your delegate wallet/node, the forging tab will show you the blocks you have forged

Passion_ltc

hero member

Activity: 714

Merit: 500

Crypti Community Manager

Quote from: patmast3r on May 15, 2015, 08:45:49 AM

Quote from: Litoshi on May 13, 2015, 06:22:45 AM

Quote from: patmast3r on May 13, 2015, 06:00:01 AM

Quote from: Litoshi on May 13, 2015, 05:57:32 AM

Quote from: patmast3r on May 13, 2015, 05:48:04 AM

Quote from: Litoshi on May 13, 2015, 04:53:15 AM

With Windows, it is not a good idea to use the full node. Use the Crypti Lite wallet instead.

There is an issue with the time sync within Windows that causes forks and the inability to sync the block chain. In future releases, Boris is not going to release Windows versions of the full wallet because of this issue. Windows versions will be Lite wallets only. Full wallets will be Linux based.

You can try deleting the blockchain.db file and restarting the node. This usually works.

What kind of issue is that ? Like what does it cause ?

With a 10 minute block time, or even a one minute per block time, the time on your windows computer can be off a few seconds from the official NIST time and still forge or sync. But with the XCR 10 second block times, a difference of a few seconds in the time on your windows machine and the network time, as synced with NIST, has caused failures to forge blocks and forking of the block chain for that machine.

It is a problem with Windows, not with Crypti.

I'm guessing because the network is rejecting blocks that are outside of a certain time threshold (like too far in the future or past) ?

If a block sent to a Windows machine, or any delegate, is not returned in sufficient time, the block is sent to the next delegate in line to forge. The only affect on the network is a 10 second or so lengthening of the present 101 block cycle. The delegate that forged that block too late is now on a possible fork. At the end of the 101 block cycle, the network self corrects all delegates that may have forked, as well as updating the votes cast during that cycle, and moving delegates in or out of the standby mode to the 101 club.

If the delegate that missed forging in time is on a fork, and it is 80 blocks down, it can take awhile to resync. Meanwhile, forging of blocks continues on the network as that delegate attempts to catch up. Now, what if that delegate is sent another block to forge before completing the block chain sync? Further forking? I dont know for sure, but it is not helping to secure the network.

I see.
It's not really a huge issue as most delegates would prob have run on linux machines anyway but you could take a look at the NEM whitepaper when it comes out. The NEM devs have implemented their own timesync protocoll which results in nodes not being more than 1-2 seconds away from each other (I'm told it's usually within ms but 1-2 s are not unthinkable).

We check every new whitepaper which appears. Thanks for the hint.

dzarmush

legendary

Activity: 1806

Merit: 1001

Quote from: Litoshi on May 15, 2015, 08:56:26 AM

Quote from: dzarmush on May 15, 2015, 08:24:34 AM

How do I check if I forge any blocks at the moment? My LA Vultr node started working worse and worse, so I deleted it and deployed the one in NY/NJ location instead of it, but as I see my uptime is keeping falling. Forging is enabled.

UPD: I checked my delegate through the web wallet, it showed that I wasn't forging. Will try to restart the server.

UPD2: It worked, my delegate is back online.

you can watch the Delegate monitor here and see when your Delegte is forging.

http://cryptichain.me/delegateMonitor

I know Delegate Monitor, but I don't see where I can check whether I'm forging or not.

Litoshi

hero member

Activity: 700

Merit: 500

Member of the Crypti Foundation Board of Directors

Quote from: patmast3r on May 15, 2015, 08:45:49 AM

Quote from: Litoshi on May 13, 2015, 06:22:45 AM

Quote from: patmast3r on May 13, 2015, 06:00:01 AM

Quote from: Litoshi on May 13, 2015, 05:57:32 AM

Quote from: patmast3r on May 13, 2015, 05:48:04 AM

Quote from: Litoshi on May 13, 2015, 04:53:15 AM

With Windows, it is not a good idea to use the full node. Use the Crypti Lite wallet instead.

There is an issue with the time sync within Windows that causes forks and the inability to sync the block chain. In future releases, Boris is not going to release Windows versions of the full wallet because of this issue. Windows versions will be Lite wallets only. Full wallets will be Linux based.

You can try deleting the blockchain.db file and restarting the node. This usually works.

What kind of issue is that ? Like what does it cause ?

With a 10 minute block time, or even a one minute per block time, the time on your windows computer can be off a few seconds from the official NIST time and still forge or sync. But with the XCR 10 second block times, a difference of a few seconds in the time on your windows machine and the network time, as synced with NIST, has caused failures to forge blocks and forking of the block chain for that machine.

It is a problem with Windows, not with Crypti.

I'm guessing because the network is rejecting blocks that are outside of a certain time threshold (like too far in the future or past) ?

If a block sent to a Windows machine, or any delegate, is not returned in sufficient time, the block is sent to the next delegate in line to forge. The only affect on the network is a 10 second or so lengthening of the present 101 block cycle. The delegate that forged that block too late is now on a possible fork. At the end of the 101 block cycle, the network self corrects all delegates that may have forked, as well as updating the votes cast during that cycle, and moving delegates in or out of the standby mode to the 101 club.

If the delegate that missed forging in time is on a fork, and it is 80 blocks down, it can take awhile to resync. Meanwhile, forging of blocks continues on the network as that delegate attempts to catch up. Now, what if that delegate is sent another block to forge before completing the block chain sync? Further forking? I dont know for sure, but it is not helping to secure the network.

I see.
It's not really a huge issue as most delegates would prob have run on linux machines anyway but you could take a look at the NEM whitepaper when it comes out. The NEM devs have implemented their own timesync protocoll which results in nodes not being more than 1-2 seconds away from each other (I'm told it's usually within ms but 1-2 s are not unthinkable).

Stas did a little testing two days ago with a Windows wallet. He reset the clock on the computer, and found that if the Windows time is off by 2 seconds, a transaction sent from that machine, would not be accepted by the network.

Litoshi

hero member

Activity: 700

Merit: 500

Member of the Crypti Foundation Board of Directors

Quote from: dzarmush on May 15, 2015, 08:24:34 AM

How do I check if I forge any blocks at the moment? My LA Vultr node started working worse and worse, so I deleted it and deployed the one in NY/NJ location instead of it, but as I see my uptime is keeping falling. Forging is enabled.

UPD: I checked my delegate through the web wallet, it showed that I wasn't forging. Will try to restart the server.

UPD2: It worked, my delegate is back online.

you can watch the Delegate monitor here and see when your Delegte is forging.

http://cryptichain.me/delegateMonitor

patmast3r

hero member

Activity: 980

Merit: 1001

Quote from: Litoshi on May 13, 2015, 06:22:45 AM

Quote from: patmast3r on May 13, 2015, 06:00:01 AM

Quote from: Litoshi on May 13, 2015, 05:57:32 AM

Quote from: patmast3r on May 13, 2015, 05:48:04 AM

Quote from: Litoshi on May 13, 2015, 04:53:15 AM

With Windows, it is not a good idea to use the full node. Use the Crypti Lite wallet instead.

There is an issue with the time sync within Windows that causes forks and the inability to sync the block chain. In future releases, Boris is not going to release Windows versions of the full wallet because of this issue. Windows versions will be Lite wallets only. Full wallets will be Linux based.

You can try deleting the blockchain.db file and restarting the node. This usually works.

What kind of issue is that ? Like what does it cause ?

With a 10 minute block time, or even a one minute per block time, the time on your windows computer can be off a few seconds from the official NIST time and still forge or sync. But with the XCR 10 second block times, a difference of a few seconds in the time on your windows machine and the network time, as synced with NIST, has caused failures to forge blocks and forking of the block chain for that machine.

It is a problem with Windows, not with Crypti.

I'm guessing because the network is rejecting blocks that are outside of a certain time threshold (like too far in the future or past) ?

If a block sent to a Windows machine, or any delegate, is not returned in sufficient time, the block is sent to the next delegate in line to forge. The only affect on the network is a 10 second or so lengthening of the present 101 block cycle. The delegate that forged that block too late is now on a possible fork. At the end of the 101 block cycle, the network self corrects all delegates that may have forked, as well as updating the votes cast during that cycle, and moving delegates in or out of the standby mode to the 101 club.

If the delegate that missed forging in time is on a fork, and it is 80 blocks down, it can take awhile to resync. Meanwhile, forging of blocks continues on the network as that delegate attempts to catch up. Now, what if that delegate is sent another block to forge before completing the block chain sync? Further forking? I dont know for sure, but it is not helping to secure the network.

I see.
It's not really a huge issue as most delegates would prob have run on linux machines anyway but you could take a look at the NEM whitepaper when it comes out. The NEM devs have implemented their own timesync protocoll which results in nodes not being more than 1-2 seconds away from each other (I'm told it's usually within ms but 1-2 s are not unthinkable).

dzarmush

legendary

Activity: 1806

Merit: 1001

How do I check if I forge any blocks at the moment? My LA Vultr node started working worse and worse, so I deleted it and deployed the one in NY/NJ location instead of it, but as I see my uptime is keeping falling. Forging is enabled.

UPD: I checked my delegate through the web wallet, it showed that I wasn't forging. Will try to restart the server.

UPD2: It worked, my delegate is back online.

GreXX

hero member

Activity: 518

Merit: 500

Quote from: MalReynolds on May 14, 2015, 08:40:32 AM

Second, I totally agree about the vulnerability of Crypti in its current form to DDoS attacks. As I have discussed before, one solution is to split Top Delegate communications with Lite clients and their communications with each other onto separate IP addresses. Top Delegates should have their own darknet where only they know the IP addresses being used for communications to new forge new blocks.

Mal, I actually addressed this in some of the proposals I had for our 2.0 network when we started looking into re-working it. The problem with setting up tunnels between the delegates is that it then becomes much more difficult to hot swap in standby delegates when an active delegate gets dropped. Bot impossible mind you, just more difficult. That being said, to DDoS effectively 101 cloud servers with proper DDoS protection through cloudflare or otherwise, would be almost impossible. That's not to say all delegates will have proper security and right now I imagine many have rudimentary measures. Even then, I challenge anyone to try it and show us how vulnerable we are in the current state. I will offer some form of bounty (and i'm sure others would chip in) to anyone who can take down the network and prove they did it, or find a vulnerability.

GreXX

hero member

Activity: 518

Merit: 500

Quote from: starik69 on May 14, 2015, 06:39:38 AM

Quote from: GreXX on May 14, 2015, 12:04:37 AM

Starik, if someone were to run a full node on windows and try to become a delegate, it would be pointless. As soon as they became a delegate and were active and started missing blocks, they would just get voted out. So what is the point of supporting full nodes for windows? Full nodes aren't meant to be run by the average user. The Lite Wallet can interface with the delegates for anyone on a Windows box, but no one running an application, PoS, or otherwise would be running windows anyways.

Your argument is irrelevant because i never suggested to make a delegate on Windows. Tongue

Correct me if i am wrong. Roll Eyes

Lite wallet does not check blockchain or blocks or transactions and does not propagate them through network. It only connects to delegate nodes. Sad

While full wallet does. (as on the most other cryptocurrencies) Cool

If this is true and the network became only 101 delegates then this is very bad because it could be stopped by simple ddos attack. Cry

BTW, will lite wallet run DAPPs? Huh

For reference, if you think a simple DDoS attack can take down the network, I will pay you a bounty to prove it right now.

Topic: [XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 83. (Read 804672 times)