Pages:
Author

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

hero member
Activity: 546
Merit: 500
Just a heads up, the Crypti Dapp docs on GitHub are outdated, or simply aren't correct. I tried to set up an environment on Linux (Ubuntu 15.04) following this tutorial to the tee : https://github.com/crypti/crypti-dapps-docs/blob/master/EnvironmentSetup.md, but was unable to. The Testnet Client simply doesn't install properly, with the current instructions.

Currently there are 0 DApps submitted by the community,  0. I'm trying to fiddle around with creating one, but nobody seems to care about this. Max and Olivier were the only people that used to respond to these questions, and it seems like once they've left nobody else wants to answer them.

We definitely apologize for the delay in getting an answer, but we are working to get through the immediate issues with delegates and materials that were removed or taken down in the last few days. As soon as we finish we will take a look at the docs. I will ask Boris if he can take a look sooner, but please be patient as we work through the immediately pressing issues. I believe this was brought up yesterday and we simply haven't gotten there yet. It's not being ignored I assure you.

Considering the fact that there have been 0 submitted entries to the DApp contest, and I would like to build one, is there any chance the deadline could be extended? If I wasn't able to get anywhere on Linux with setting up the environment, I doubt others would have got anywhere too. The problem isn't with configuration, but with the actual client itself.

Definitely. I'd like everyone to keep bringing these and I am making an immediate list of action items to address with the Foundation. I am hoping we can have a meeting Saturday on Crypti Chat (Rocket Chat Server) so you guys can all sit in and add any additional issues / talking points.
Sure, decide on a time and I'll be there.
hero member
Activity: 518
Merit: 500
Just a heads up, the Crypti Dapp docs on GitHub are outdated, or simply aren't correct. I tried to set up an environment on Linux (Ubuntu 15.04) following this tutorial to the tee : https://github.com/crypti/crypti-dapps-docs/blob/master/EnvironmentSetup.md, but was unable to. The Testnet Client simply doesn't install properly, with the current instructions.

Currently there are 0 DApps submitted by the community,  0. I'm trying to fiddle around with creating one, but nobody seems to care about this. Max and Olivier were the only people that used to respond to these questions, and it seems like once they've left nobody else wants to answer them.

We definitely apologize for the delay in getting an answer, but we are working to get through the immediate issues with delegates and materials that were removed or taken down in the last few days. As soon as we finish we will take a look at the docs. I will ask Boris if he can take a look sooner, but please be patient as we work through the immediately pressing issues. I believe this was brought up yesterday and we simply haven't gotten there yet. It's not being ignored I assure you.

Considering the fact that there have been 0 submitted entries to the DApp contest, and I would like to build one, is there any chance the deadline could be extended? If I wasn't able to get anywhere on Linux with setting up the environment, I doubt others would have got anywhere too. The problem isn't with configuration, but with the actual client itself.

Definitely. I'd like everyone to keep bringing these and I am making an immediate list of action items to address with the Foundation. I am hoping we can have a meeting Saturday on Crypti Chat (Rocket Chat Server) so you guys can all sit in and add any additional issues / talking points.
hero member
Activity: 546
Merit: 500
Just a heads up, the Crypti Dapp docs on GitHub are outdated, or simply aren't correct. I tried to set up an environment on Linux (Ubuntu 15.04) following this tutorial to the tee : https://github.com/crypti/crypti-dapps-docs/blob/master/EnvironmentSetup.md, but was unable to. The Testnet Client simply doesn't install properly, with the current instructions.

Currently there are 0 DApps submitted by the community,  0. I'm trying to fiddle around with creating one, but nobody seems to care about this. Max and Olivier were the only people that used to respond to these questions, and it seems like once they've left nobody else wants to answer them.

We definitely apologize for the delay in getting an answer, but we are working to get through the immediate issues with delegates and materials that were removed or taken down in the last few days. As soon as we finish we will take a look at the docs. I will ask Boris if he can take a look sooner, but please be patient as we work through the immediately pressing issues. I believe this was brought up yesterday and we simply haven't gotten there yet. It's not being ignored I assure you.

Considering the fact that there have been 0 submitted entries to the DApp contest, and I would like to build one, is there any chance the deadline could be extended? If I wasn't able to get anywhere on Linux with setting up the environment, I doubt others would have got anywhere too. The problem isn't with configuration, but with the actual client itself.
hero member
Activity: 518
Merit: 500
Just a heads up, the Crypti Dapp docs on GitHub are outdated, or simply aren't correct. I tried to set up an environment on Linux (Ubuntu 15.04) following this tutorial to the tee : https://github.com/crypti/crypti-dapps-docs/blob/master/EnvironmentSetup.md, but was unable to. The Testnet Client simply doesn't install properly, with the current instructions.

Currently there are 0 DApps submitted by the community,  0. I'm trying to fiddle around with creating one, but nobody seems to care about this. Max and Olivier were the only people that used to respond to these questions, and it seems like once they've left nobody else wants to answer them.

We definitely apologize for the delay in getting an answer, but we are working to get through the immediate issues with delegates and materials that were removed or taken down in the last few days. As soon as we finish we will take a look at the docs. I will ask Boris if he can take a look sooner, but please be patient as we work through the immediately pressing issues. I believe this was brought up yesterday and we simply haven't gotten there yet. It's not being ignored I assure you.
hero member
Activity: 546
Merit: 500
Just a heads up, the Crypti Dapp docs on GitHub are outdated, or simply aren't correct. I tried to set up an environment on Linux (Ubuntu 15.04) following this tutorial to the tee : https://github.com/crypti/crypti-dapps-docs/blob/master/EnvironmentSetup.md, but was unable to. The Testnet Client simply doesn't install properly, with the current instructions.

Currently there are 0 DApps submitted by the community,  0. I'm trying to fiddle around with creating one, but nobody seems to care about this. Max and Olivier were the only people that used to respond to these questions, and it seems like once they've left nobody else wants to answer them.
hero member
Activity: 504
Merit: 500
Communications Lead
Getting the Crypti DPoS system healthy is the first priority for Crypti to survive.

A massive reshuffle of Crypti votes in the past few days has left the DPoS system reeling.  Currently over 30% of DPoS Active Delegates are offline, and soon an additional 35% of Active Delegates will go offline, too.

17 "Long-Time" Delegates That Are Currently Offline:

amanai
arman
Azkhabar
boris
cryptiNeo
Dragon88
escrow
Ferrari
HolyGrail
lead.developer
Lenticularis
LesPaul
masterforger
peanuts
poker
TwoTime
wsec

15 "New" Active Delegates That Have Apparently Not Yet Set Up A Node, So Also Currently Offline:

An additional 15 new recruits have apparently gone from Standby to Active, and they obviously have not set up a node yet.  Hopefully they will...if only they could be contacted. (THIS IS WHY I HAVE ADVOCATED GATHERING EMAIL ADDRESSES IN THE CLIENT WHEN SIGNING UP TO BE A DELEGATE - MAYBE YOU GUYS WILL IMPLEMENT THIS NOW?).  They will probably need help if / when they set up a node, a role previously done mainly by Max and Olivier...

belpheg
btc
checkraiser
eth
Gabes.bit
GermanWhite
hansolo
Karasur
Lemix
nrp
Pioneerbear
Ratnet
whit
xhipster
xortrox

32 Currently Forging Nodes By Olivier / Max That Will Go Offline Soon:

Olivier is currently running an additional 29 Crypti nodes he will be shutting down on March 21.  Max is running at least 3 more Crypti nodes, maybe more, that are going away also.

Aetherfields
AncientIsland
AuroraBorealis
BlackSands
CircularRuins
CryptiChain
CryptiChat
CryptiKit
Eden
EyesDown
Filaments
FirstRain
FoldedSpace
Helios
HiddenRefuge
InvisibleTemple
Kamoukie
Karmacoma
Karmacrypto
Kiara
Koronoko
LostCaverns
Lyra
Nyx
Olivier
Tchamantche
Telomere
Verbena
Zen

Max
CHIP
Raspberry Pi

Do the math.  To get to 101 Forging Delegates, 17 + 15 + 29 + 3 = 64 Crypti nodes need to be set up by March 21 - less than 60 days away.

26 Current Standby Delegates / New Community Members Who Could Go Online

Here's 26 current standby delegates who are not original Crypti Foundation nodes.  I recommend voting these individuals up.  We know nothing about them other than their demonstrated willingness to join Crypti and their desire to participate.  In desperate times, that's enough.  If only we knew their emails and could contact them...oh wait, I already ranted on that above.

Barie
Borpf
Crypti4all
DonaldTrump
dx101
ern
forykw
Hubtm.VR
Intrinsic1
Intrinsic2
ligaya9
maigj
NateDangerous
Nrp2
Pikachu
Roland
shop
Smalik
SwampAngel
team
Technologov
test_delegate
th40
Vinter
Wulfcastle
yuhiesirs

Keep Track Of The Numbers Here:

https://cryptichain.lisk.io/delegateMonitor




http://live.crypti.me/ is live, it is using Oliviers repository from the cryptichain.me site. No more linking into Crypti's temporary blockchain explorer Smiley
sr. member
Activity: 432
Merit: 250
I was actually going to build a cluster of 10 Bitseeds (bitseed.org) to do this but it turns out multiple delegates can run on a single CPU since they run sequentially.
hero member
Activity: 756
Merit: 501
We need something like that:  Grin

hero member
Activity: 756
Merit: 501
I just started my Crypti Pi2 Node again. Named Borpf like here at Bitcointalk.
Its only one, but every one is a part of something bigger. Wink
legendary
Activity: 938
Merit: 1000
Getting the Crypti DPoS system healthy is the first priority for Crypti to survive.

A massive reshuffle of Crypti votes in the past few days has left the DPoS system reeling.  Currently over 30% of DPoS Active Delegates are offline, and soon an additional 35% of Active Delegates will go offline, too.

17 "Long-Time" Delegates That Are Currently Offline:

amanai
arman
Azkhabar
boris
cryptiNeo
Dragon88
escrow
Ferrari
HolyGrail
lead.developer
Lenticularis
LesPaul
masterforger
peanuts
poker
TwoTime
wsec

15 "New" Active Delegates That Have Apparently Not Yet Set Up A Node, So Also Currently Offline:

An additional 15 new recruits have apparently gone from Standby to Active, and they obviously have not set up a node yet.  Hopefully they will...if only they could be contacted. (THIS IS WHY I HAVE ADVOCATED GATHERING EMAIL ADDRESSES IN THE CLIENT WHEN SIGNING UP TO BE A DELEGATE - MAYBE YOU GUYS WILL IMPLEMENT THIS NOW?).  They will probably need help if / when they set up a node, a role previously done mainly by Max and Olivier...

belpheg
btc
checkraiser
eth
Gabes.bit
GermanWhite
hansolo
Karasur
Lemix
nrp
Pioneerbear
Ratnet
whit
xhipster
xortrox

32 Currently Forging Nodes By Olivier / Max That Will Go Offline Soon:

Olivier is currently running an additional 29 Crypti nodes he will be shutting down on March 21.  Max is running at least 3 more Crypti nodes, maybe more, that are going away also.

Aetherfields
AncientIsland
AuroraBorealis
BlackSands
CircularRuins
CryptiChain
CryptiChat
CryptiKit
Eden
EyesDown
Filaments
FirstRain
FoldedSpace
Helios
HiddenRefuge
InvisibleTemple
Kamoukie
Karmacoma
Karmacrypto
Kiara
Koronoko
LostCaverns
Lyra
Nyx
Olivier
Tchamantche
Telomere
Verbena
Zen

Max
CHIP
Raspberry Pi

Do the math.  To get to 101 Forging Delegates, 17 + 15 + 29 + 3 = 64 Crypti nodes need to be set up by March 21 - less than 60 days away.

26 Current Standby Delegates / New Community Members Who Could Go Online

Here's 26 current standby delegates who are not original Crypti Foundation nodes.  I recommend voting these individuals up.  We know nothing about them other than their demonstrated willingness to join Crypti and their desire to participate.  In desperate times, that's enough.  If only we knew their emails and could contact them...oh wait, I already ranted on that above.

Barie
Borpf
Crypti4all
DonaldTrump
dx101
ern
forykw
Hubtm.VR
Intrinsic1
Intrinsic2
ligaya9
maigj
NateDangerous
Nrp2
Pikachu
Roland
shop
Smalik
SwampAngel
team
Technologov
test_delegate
th40
Vinter
Wulfcastle
yuhiesirs

Keep Track Of The Numbers Here:

http://live.crypti.me/


hero member
Activity: 518
Merit: 500
There is a trust system in place for delegates. DELEGATE VOTING

If you dont know who a delgate is owned by, dont vote for them

If a delegate has lousy up time, vote them down




Exactly, this information should be clearly visible and public when you are in the act of voting. At the moment, it is not. You would need to scour the crippled forums of forum.crypti.me to find who's the owner of which delegate.

This is definitely an interesting aspect of future development options. I have often argued within the Foundation that we really need to focus on the dapp store and web presence (front-end) of the network as a possible avenue to increase the capability and function of the entire network. Storing descriptions of delegate accounts, avatars / photos, links, reviews, etc, would be a lot to store on the blockchain and over time might cause too much bloat. There is no reason why those features can't be run as a web property by the Foundation or a company to incorporate all of the information using traditional means. You could store the vote (for reviews) and ratings on the blockchain to ensure they were secure and as unbiased as possible. At the end of the day, developers want an easy to use system that allows them to distribute their applications with ease, in a feature rich environment, with a strong discovery system to allow people to find them. This is why my argument for months, is that now that we are nearing the completion of the core network features, our focus should be on expanding the functionality of the dapp store, discovery engine, and possibly even an advertising engine (or allowing one to be easily incorporated), as well as creating our own well developed and feature rich dapps for the store. I strongly believe that the dapp store itself is one of our strongest properties moving forward and has a lot of room for expansion of features.

Of course these are just my thoughts... But i'm always interested to hear from you guys about this stuff.
hero member
Activity: 700
Merit: 500
Member of the Crypti Foundation Board of Directors
There is a trust system in place for delegates. DELEGATE VOTING

If you dont know who a delgate is owned by, dont vote for them

If a delegate has lousy up time, vote them down




Exactly, this information should be clearly visible and public when you are in the act of voting. At the moment, it is not. You would need to scour the crippled forums of forum.crypti.me to find who's the owner of which delegate.

Thats my point....... If the name of the delegate does not tell you who owns it, dont vote for it.  If a delegate owner wants votes, they need to make their ownership self-evident.  No one should have to do dep research for this.
hero member
Activity: 504
Merit: 500
Communications Lead
There is a trust system in place for delegates. DELEGATE VOTING

If you dont know who a delgate is owned by, dont vote for them

If a delegate has lousy up time, vote them down




Exactly, this information should be clearly visible and public when you are in the act of voting. At the moment, it is not. You would need to scour the crippled forums of forum.crypti.me to find who's the owner of which delegate.
hero member
Activity: 700
Merit: 500
Member of the Crypti Foundation Board of Directors
There is a trust system in place for delegates. DELEGATE VOTING

If you dont know who a delgate is owned by, dont vote for them

If a delegate has lousy up time, vote them down


hero member
Activity: 504
Merit: 500
Communications Lead
I personally think 101 delegates are too much, untill XCR gets bigger.

Can the number of Delegates be lowered? How does it affect the network? Is this something you could decrease and/or increase with ease?

It is at 101 to make a 51% attack very hard.

Because of the 10 second block time, and the 6-10 confirms for transactions, a large number of forging nodes is necessary to insure that a random set chosen to confirm a transaction are not all trojan nodes designed to steal the XCR or to foul up the network. 


This would be accurate if the 101 Club had 101 individual people running a single server.  The current setup, with Olivier running 35 of the 101 servers, not so much.  Crypti cannot claim to be secure as long as just a few Foundation members control the top 101 servers - as we have seen.  Expanded community involvement is a must. 

@ bitseed:  Need a 2GB ARMv7 board?  Take a look at the Odroid XU4:

http://www.hardkernel.com/main/products/prdt_info.php

Exactly my point. I understand the decentralized aspect of the coin, but if we cannot find those 101 delegates then what's the point? Crypti needs to reconsider every aspect of DPoS, as it is, it's a hindrance more than a success. The same question keeps popping up over and over again, what's the reward of being a delegate (other then to toss Crypti a bone and secure the network)? The fee is too low, forging rewards are lower than $5 a month. There needs to be more incentive in order for people to delegate and join the club. Crypti does not have enough. 

Also, there needs to be a way to know who is running which delegate. Some kind of trust/verified delegate system to secure the network.
full member
Activity: 225
Merit: 100
Oh

And by the way

This thread is moving

Keep it moving and foundations members be loud and proud

Time to get some
full member
Activity: 225
Merit: 100
I'd  like to thank Max
You have given this community a kick up the ass
To your chagrin or otherwise Max
Watch this space

With a bang, not a whimper

Savvy?

Let's do this

PS my biggest concern is this DPOS thing. Seems dangerously complex.
PPS if things go well in a short time I will confidently state this is THE most undervalued crypto in this space.
legendary
Activity: 938
Merit: 1000
I personally think 101 delegates are too much, untill XCR gets bigger.

Can the number of Delegates be lowered? How does it affect the network? Is this something you could decrease and/or increase with ease?

It is at 101 to make a 51% attack very hard.

Because of the 10 second block time, and the 6-10 confirms for transactions, a large number of forging nodes is necessary to insure that a random set chosen to confirm a transaction are not all trojan nodes designed to steal the XCR or to foul up the network. 


This would be accurate if the 101 Club had 101 individual people running a single server.  The current setup, with Olivier running 35 of the 101 servers, not so much.  Crypti cannot claim to be secure as long as just a few Foundation members control the top 101 servers - as we have seen.  Expanded community involvement is a must. 

@ bitseed:  Need a 2GB ARMv7 board?  Take a look at the Odroid XU4:

http://www.hardkernel.com/main/products/prdt_info.php
hero member
Activity: 546
Merit: 500
Just a heads up, the Crypti Dapp docs on GitHub are outdated, or simply aren't correct. I tried to set up an environment on Linux (Ubuntu 15.04) following this tutorial to the tee : https://github.com/crypti/crypti-dapps-docs/blob/master/EnvironmentSetup.md, but was unable to. The Testnet Client simply doesn't install properly, with the current instructions.
hero member
Activity: 511
Merit: 500
Boris, Crypti Lead Developer, Lisk Advisor
I am still trying to wrap my head around all of this.  I need answers to questions.

1. The current versions of Crypti that have been released are 0.5.2 for the Crypti wallet client and 0.5.4 for Delegates, right?  0.5.2 is a "light" version that only allows transactions and 0.5.4 creates new blocks, right?

2. There is a 0.5.5 version under test that has not yet been released to the public, right?  Is this a client wallet version for making transactions or a Delegate version that writes to the blockchain?  

3. What are the main new features that will go online with 0.5.5?

4. What is the target release date for Crypti 0.5.5?

5. When will Crypti 0.5.5 source code be released via Github?

6. Did Max / Olivier have access to Crypti 0.5.5 code to use it for the basis of a fork?  Or will their fork be based on Crypti 0.5.2 / 0.5.4?

Are there concrete answers for these questions?

1. 0.5.4 doesn't effect lite wallet, so, lite wallet could work with 0.5.4
2. We going to close fast loading for small devices, because Crypti work perfect on devices with slow cpu and ram, but loading of blockchain takes time.  And we have latest UI versions that contains mobile view.
3. Already released. All sources, include crypti, frontend, and crypti-js. See my previous messages.
4. Yes, they had access.
Pages:
Jump to: