Pages:
Author

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

hero member
Activity: 714
Merit: 500
Crypti Community Manager
Just one suggestion, with regards to the UI Design. It seems like you guys are using a generic typeface, it seems like either Arial, or Helevetica Nueue.

Id personally suggest either using Montserrat or Proxima Nova, both are terrific typefaces which suit just about any design. Once integrated, you'll realize how good they actually look.

Montserrat (free through Google Fonts) : https://www.google.com/fonts/specimen/Montserrat

Proxima Nova (paid through TypeKit) : https://typekit.com/fonts/proxima-nova


We are using Roboto, like the google material design guideline suggests. It's the most typical font for material design and already used at http://crypti.me


Check it out: http://www.google.com/design/spec/style/typography.html#typography-typeface

But please check your fonts in the blog section they differ from the rest of the site.
While you are using sans-serif; style on the site, the blog menus are all in serif; fonts.



We will take a look. Thank you. Smiley

We took a look, for us it's working. Which OS do you use? Which browser? Which native OS language?




Edit: We may have found the issue.

Were you able to fix it? The CSS itself is fine everything looks good, problem is with Cross Domain Resource Sharing policy in the sub domain which is blocking the font from being loaded.

Message from Boris:

boris [3:21 PM]
yes
boris [3:21 PM]
i will fix today

Should be fixed.
hero member
Activity: 714
Merit: 500
Crypti Community Manager
BTW starik69, I voted for your delegate...
Thank you! Cool
But as of now Crypti is not a currency, it is a closed club controlled by devs Cry
In the absence of users/community only their votes matter. Roll Eyes
Because i am telling them truth i doubt they will vote for my delegate. Grin
But it is funny how they discredit their own work Cheesy

You should see XCR as a token to fuel the network. Later on it can be used for the Dapps, for messages and much more. We are more than just a currency.
legendary
Activity: 1367
Merit: 1000
BTW starik69, I voted for your delegate...
Thank you! Cool
But as of now Crypti is not a currency, it is a closed club controlled by devs Cry
In the absence of users/community only their votes matter. Roll Eyes
Because i am telling them truth i doubt they will vote for my delegate. Grin
But it is funny how they discredit their own work Cheesy
hero member
Activity: 700
Merit: 500
Member of the Crypti Foundation Board of Directors
Anyone using Vultr, check your account.  They just shut off several of our delegate nodes because they have changed how they bill for services.

We are rebooting them.

full member
Activity: 178
Merit: 100
LiskHQ CTO
Code:
Worst Uptime

100.00%

by dzarmush
Huh Huh Huh

Refresh your page. I fixed a few small bugs this afternoon related to new delegates.



BTW starik69, I voted for your delegate...
legendary
Activity: 1367
Merit: 1000
Code:
Worst Uptime

100.00%

by dzarmush
Huh Huh Huh
legendary
Activity: 1344
Merit: 1001
hero member
Activity: 714
Merit: 500
Crypti Community Manager
Welcome dzarmush to the 101 club!  Cool
hero member
Activity: 714
Merit: 500
Crypti Community Manager
Just one suggestion, with regards to the UI Design. It seems like you guys are using a generic typeface, it seems like either Arial, or Helevetica Nueue.

Id personally suggest either using Montserrat or Proxima Nova, both are terrific typefaces which suit just about any design. Once integrated, you'll realize how good they actually look.

Montserrat (free through Google Fonts) : https://www.google.com/fonts/specimen/Montserrat

Proxima Nova (paid through TypeKit) : https://typekit.com/fonts/proxima-nova


We are using Roboto, like the google material design guideline suggests. It's the most typical font for material design and already used at http://crypti.me


Check it out: http://www.google.com/design/spec/style/typography.html#typography-typeface

But please check your fonts in the blog section they differ from the rest of the site.
While you are using sans-serif; style on the site, the blog menus are all in serif; fonts.



We will take a look. Thank you. Smiley

We took a look, for us it's working. Which OS do you use? Which browser? Which native OS language?




Edit: We may have found the issue.

Were you able to fix it? The CSS itself is fine everything looks good, problem is with Cross Domain Resource Sharing policy in the sub domain which is blocking the font from being loaded.

Message from Boris:

boris [3:21 PM]
yes
boris [3:21 PM]
i will fix today
member
Activity: 71
Merit: 10
Just one suggestion, with regards to the UI Design. It seems like you guys are using a generic typeface, it seems like either Arial, or Helevetica Nueue.

Id personally suggest either using Montserrat or Proxima Nova, both are terrific typefaces which suit just about any design. Once integrated, you'll realize how good they actually look.

Montserrat (free through Google Fonts) : https://www.google.com/fonts/specimen/Montserrat

Proxima Nova (paid through TypeKit) : https://typekit.com/fonts/proxima-nova


We are using Roboto, like the google material design guideline suggests. It's the most typical font for material design and already used at http://crypti.me


Check it out: http://www.google.com/design/spec/style/typography.html#typography-typeface

But please check your fonts in the blog section they differ from the rest of the site.
While you are using sans-serif; style on the site, the blog menus are all in serif; fonts.



We will take a look. Thank you. Smiley

We took a look, for us it's working. Which OS do you use? Which browser? Which native OS language?




Edit: We may have found the issue.

Were you able to fix it? The CSS itself is fine everything looks good, problem is with Cross Domain Resource Sharing policy in the sub domain which is blocking the font from being loaded.
member
Activity: 71
Merit: 10
Crypti Design Preview

Today I want to show you something we worked on for quite a while already, a new design for our client. We as a team wanted a sleek, intuitive and familiar user interface. Therefore we decided to go with the Google material design guidelines. And in our opinion it was the right decision, our designer created something really beautiful!

To keep as close as possible to the Crypti design, we still use the three official Crypti colors (green, blue, purple). Based on this we build up an entirely new user interface for our client. With this we make it truly awesome!

For now we show you three pages; "Dashboard", "Dapp Store" and "Forging". Starting next Thursday, we will take a detailed look at the different pages.

We will introduce the new design with the next major update (v0.3.0), at that point it will not contain everything the preview reveals. This will happen from time to time, along with our backend feature releases.


Stay tuned, there is still so much more to come for Crypti and we truly believe, that we create something huge here!

The Crypti Foundation

I just saw the new design. I'm stunned this is amazing, keep up the good work.
member
Activity: 110
Merit: 10
Also in the 'Delegate Monitor' page, is there a way to identify which of the delegates belong to the initial 101 setup to start off DPOS and which are the ones setup later by community or devs ?
Mal made a list of all initial 101 delegates. You can find it here: http://forum.crypti.me/viewtopic.php?f=17&t=42

Would be cool, if you set up a delegate. We need more from the community. Smiley

Thanks for list of 101 delegates.

I remember reading that the initial 101 delegates would always be there as a failover/fallback delegate even if none of these were among the 101 forging delegates at the time.

If this is the case, was wondering whether it would be useful to have some sort of marking to identify/differentiate these delegates on the 'Delegate Monitor' page ?

 am not sure what kind of marking you are asking for.  The top 101 delegates will always be able to forge, IF THEY HAVE FORGING ENABLED.  If a 101 club delegate stopped forging, they would still be in the top unless they were voted down.  There is no present way to delete a delegate or to move a standby into the 101 club other than by votes.

It would be more expeditious if a delegate were to be bumped out of the top 101 for having X number of blocks in a row fail to forge, or if uptime fell below a certain number.  But that is not in the code right now.

Presently, votes control everything.  


Suggestions:

1. Implement a system to replace poor performing Top Delegates with top-voted Standby Delegates if Top Delegate performance falls below pre-set minimum performance limits.

2. The list of the original 101 Foundation delegates needs to be hard-coded in 0.2.1 client code.  Anytime there is a click on the "Delegates" link in the Client, the resulting list of Top Delegates and Standby Delegates can be color coded by reference to this list on whether or not they are Original Foundation Delegates.

Yes, I was asking/thinking something like this.
sr. member
Activity: 432
Merit: 250

Using Crypti on a smartphone, purchase a relatively small item like a candy bar from a vendor running a Lite client on a small black box.


In Northern Europe, especially the Scandinavian countries, you have been aboe to do this for 20 years.  With your Nokia Phone, you call the number listed on the vending machine, and select your item, then they bill your phone by deducting the amount from your SIM card balance.

And we can extend that vending machine functionality to ANY vendor with a cheap online Raspberry Pi 2 running Crypti Lite.  The smartphone displays a QR code of the Crypti account to be debited, the Raspberry Pi built-in camera reads it and immediately puts the transaction on the blockchain.

Now THAT will be MEGA huge when it shows up on 0.7.0...



We have Crypti running on our unit, https://bitseed.org/product/blockchain-node-developer-version/ . The full production version will sell for around $100, current developer version is $149. This unit includes a 160GB hard drive and has MIPS for connecting a camera. The Raspi also needs to have a camera added. We settled on the pcduino3 nano, http://www.linksprite.com/?page_id=815 since it includes 4Gb of onboard emmc flash and SATA with power for connecting a hard drive or SSD. It also has Arduino headers, which we will be using for an internal battery backup, and can be used to connect other devices as well. For a vending machine, these could be controllers for actuators to release products, motors for conveyors, and sensors for inventory management.
legendary
Activity: 938
Merit: 1000
Also in the 'Delegate Monitor' page, is there a way to identify which of the delegates belong to the initial 101 setup to start off DPOS and which are the ones setup later by community or devs ?
Mal made a list of all initial 101 delegates. You can find it here: http://forum.crypti.me/viewtopic.php?f=17&t=42

Would be cool, if you set up a delegate. We need more from the community. Smiley

Thanks for list of 101 delegates.

I remember reading that the initial 101 delegates would always be there as a failover/fallback delegate even if none of these were among the 101 forging delegates at the time.

If this is the case, was wondering whether it would be useful to have some sort of marking to identify/differentiate these delegates on the 'Delegate Monitor' page ?

 am not sure what kind of marking you are asking for.  The top 101 delegates will always be able to forge, IF THEY HAVE FORGING ENABLED.  If a 101 club delegate stopped forging, they would still be in the top unless they were voted down.  There is no present way to delete a delegate or to move a standby into the 101 club other than by votes.

It would be more expeditious if a delegate were to be bumped out of the top 101 for having X number of blocks in a row fail to forge, or if uptime fell below a certain number.  But that is not in the code right now.

Presently, votes control everything.  


Suggestions:

1. Implement a system to replace poor performing Top Delegates with top-voted Standby Delegates if Top Delegate performance falls below pre-set minimum performance limits.

2. The list of the original 101 Foundation delegates needs to be hard-coded in 0.2.1 client code.  Anytime there is a click on the "Delegates" link in the Client, the resulting list of Top Delegates and Standby Delegates can be color coded by reference to this list on whether or not they are Original Foundation Delegates.

3. Another column needs to be added with a "Current Consecutive Missed Cycles" (CCMC) statistic for each Delegate to go along with their "uptime".   A 101 Club Delegate could leave the system permanently without notice and his uptime would degrade only very slowly.  It might take weeks or even months for his uptime statistic getting bad enough to alert users of the need to downvote him.  However, such a vanished Forging Delegate would have a sky-high CCMC score of 85 after only 24 hours.

4. The current Top Delegate sort is by popularity, not performance.  This is backwards.  The Top Delegate sort needs to be by uptime or preferably CCMC, not votes.  Poor-performing delegates should be in the position of highest visibility at the top of the list, perhaps color coded red if their uptime / CCMC scores fall below a minimum desirable threshold.  A Lite Wallet user should not have to search all 101 delegates looking for poor uptimes scattered occasionally among mostly high uptime figures.

5. I still think we should rebrand the "Crypti Lite" software as "Crypti Wallet", and the current "Crypti" software as "Crypti Delegate" or "Crypti Node".

I'm gonna cross-post these suggestions over in the Suggestion Box on the other forum.
hero member
Activity: 700
Merit: 500
Member of the Crypti Foundation Board of Directors
why xcr so cheap again?

thin markets.  Several people dumped 10,000 XCR on the exchanges all at once.  I can only assume they were saving it to be a delegate, but due to fee lowered to 100 XCR, and because you dont need to have any XCR in your wallet to forge, they dumped it.  Could also be that they found out that it is not possible to forge as a delegate from your home computer, so they dumped.



that means it is a great time to buy more XCR, as it is close to the IPO price

legendary
Activity: 1344
Merit: 1001
why xcr so cheap again?

People are impatient and some of them sell. Add to this market manipulators and you have mix of reasons :p
legendary
Activity: 1540
Merit: 1016
hero member
Activity: 700
Merit: 500
Member of the Crypti Foundation Board of Directors
Also in the 'Delegate Monitor' page, is there a way to identify which of the delegates belong to the initial 101 setup to start off DPOS and which are the ones setup later by community or devs ?
Mal made a list of all initial 101 delegates. You can find it here: http://forum.crypti.me/viewtopic.php?f=17&t=42

Would be cool, if you set up a delegate. We need more from the community. Smiley

Thanks for list of 101 delegates.

I remember reading that the initial 101 delegates would always be there as a failover/fallback delegate even if none of these were among the 101 forging delegates at the time.

If this is the case, was wondering whether it would be useful to have some sort of marking to identify/differentiate these delegates on the 'Delegate Monitor' page ?

 am not sure what kind of marking you are asking for.  The top 101 delegates will always be able to forge, IF THEY HAVE FORGING ENABLED.  If a 101 club delegate stopped forging, they would still be in the top unless they were voted down.  There is no present way to delete a delegate or to move a standby into the 101 club other than by votes.

It would be more expedicious if a delegate were to be bumped out of the top 101 for having X number of blocks in a row fail to forge, or if uptime fell below a certain number.  But that is not in the code right now.

Presently, votes control everything. 
member
Activity: 110
Merit: 10
Also in the 'Delegate Monitor' page, is there a way to identify which of the delegates belong to the initial 101 setup to start off DPOS and which are the ones setup later by community or devs ?
Mal made a list of all initial 101 delegates. You can find it here: http://forum.crypti.me/viewtopic.php?f=17&t=42

Would be cool, if you set up a delegate. We need more from the community. Smiley

Thanks for list of 101 delegates.

I remember reading that the initial 101 delegates would always be there as a failover/fallback delegate even if none of these were among the 101 forging delegates at the time.

If this is the case, was wondering whether it would be useful to have some sort of marking to identify/differentiate these delegates on the 'Delegate Monitor' page ?
hero member
Activity: 714
Merit: 500
Crypti Community Manager

Okay, I started 0.2.0 client on my win laptop and its been more than a hour now but still not there at the map - is it because the client is still synchronizing ? or do I need to be on 0.2.a ?

As noted above, you need to be on 0.2.0a no matter what. 

If you want to forge as a Delegate, so far the evidence has been you need to be on a cloud server like Amazon Web Service (AWS), Digital Ocean or Vultr.  Check the Original Post on Page 1 of this thread for guides on how to do this.  AWS is free for a year, you can get $5 per month service on DO and V.  Apparently home internet service has too much lag and delay to cooperate correctly in the 10 second blocktime.

I asked Cryptsy about Crypti withdrawal, they said they were working on it.  Obviously not at a very high priority level.



If AWS is free for one year then why it seems most are using DO or Vultr to setup delegates ? Is there any reason behind this or is the observation incorrect ?

I'm asking because I've been thinking about setting up a delegate and want to decide which one to use.

In our tests AWS couldn't provide the needed latencies all of the time. DO or Vultr was much better. You can still try it out, though. Smiley
Pages:
Jump to: