Welcome to the Cardano_Developers telegram group! This group is for developers and anyone interested in the technical aspect/coding of Cardano.
Official Cardano Telegram Groups
Please see the Announcements Channel for details on each group.
⛔️Community Rules ⛔️
1️⃣ Be respectful and polite. Personal attacks and insults will not be tolerated and users will be banned.
2️⃣ Please make sure you choose the appropriate group for your comments and questions.
3️⃣ Keep the discussions Cardano related and always look to add value. All posts must be related to Cardano, Ada, or any projects and businesses related to the project.
4️⃣ Scare tactics, hype, FUD and fake news are prohibited. You are not allowed to post fake news or spread misinformation.
5️⃣ No spamming or low value content. Posts and comments including referral links, phishing websites, affiliate links, advertisements or duplicate content will be removed and repeat offenders will be banned.
6️⃣ Trading and price discussion is only permitted in the @CardanoTradingOfficial group and shilling is prohibited.
7️⃣ Please search for answers prior to posting. It can get frustrating for existing users if new users simply post a question that has been already been answered. Before posting, particularly if you are new, please read through the following resources:
ℹ️https://help.cardano.org/ for general Cardano FAQ and to contact the Cardano Foundation via email.
ℹ️https://daedaluswallet.io/faq for common Daedalus questions and to contact the support team.
ℹ️https://forum.cardano.org/c/communitytechnicalsupport and @CardanoCommunityTechSupport telegram group for technical support issues.
8️⃣ Please report anything that breaks the rules to the admins in the @CardanoReportToAdmin group. We need your help to make sure rules are adhered to!
🙏And finally please do respect the admins - they are all committed to helping this community grow!
question for the IOHK team: pure functional languages were chosen for the SL; Haskell & Purescript, the reasons for which I understand and 100% agree with. however Daedalus is written in regular JS, with a distinctly objective/procedural style. I was wondering what the motivation for this decision is? Components seem to mostly be declared as classes, and for example the WalletTransactionsList components has a groupBy function that in a dozen lines achieves what groupBy in ramda would do in one, whilst maintaining the same paradigms as the SL repo. It's no judgement at all; the codebase is incredibly clear and easy to get to grips with, I'm just interested to know why the decision was made
Hey, Jonn from Serokell here, hopefully it's fine if I take the floor. The leader of the Daedalus team is an insanely experienced engineer who knows better than 99% of people in the industry how to have a team of people write a sustainable imperative code, and — most importantly — how to exhaustively test its correctness. Historically, during development of CSL, the degree to which Daedalus is tested was setting a high standard for the rest of the teams working on the CSL products. Now, considering these things, and the fact that JS insdustrial programming already have all the answers to building UIs such as Daedalus, the logical decision has been made to use the skills of a great team to the fullest extent. Hope it answers the question.
Who knows what might be the advantage for this: "For example, if network diameter is 3, then block is generated and announced 3 seconds before the end of a slot"? Rather than just sending new block as soon as you received one from previous slot and created it?
Who announces a block for slot S in your model? I don't understand your suggestion. In general, we would like for the slot leader to announce their block, not someone else, thus it should be done during their slot.
Oh, yeah, I messed the idea up with "as soon as you received one from previous slot". I meant that once my slot starts I already have previous block (if everything goes well). What is the profit not to broadcast my own block immediatelly when my slot starts?
Feels like just a sensible protocol design to me. There is an idea of input endorsers discussed in the paper, so if it proves to be viable from engineering standpoint, some day transaction gatheting for issuing blocks shall become slightly more complicated, but blocks will still have to be announced in their respective slot in a timely manner.
— Jonn, CTO of Serokell.