Demystifying StarkNet accounts
IntroductionWhen trying StarkNet for the first time, it’s easy to go through the account setup without paying much attention to it. The documentation just says:Unlike Ethereum, which distinguishes between Externally Owned Accounts (EOA) and contracts, StarkNet doesn’t have this distinction. Instead, an account is represented by a deployed contract that defines the account’s logic — most notably the signature scheme that controls who can issue transactions from it.Then, you are invited to chos...
SOLID cairo - OOP-like pattern
When I learn a new language, my first focus is to build SOLID components while leveraging the feature of this new language. In this article, I would like to present a new convention we at OnlyDust are adopting with regards to cairo development. This new kind of architecture feels like object-oriented programming in a way and leverage several cairo features like:implicit parametersstructsnamespacesFollowing OpenZeppelin’s recommendations about extensibility, we aims at building nice modules th...
protostar vs nile
When starting a new project in a new programming language, there is always this question that is raised.Which framework should I choose ?For Starknet projects, there are especially 2 new frameworks I have been trying and would like to compare: protostar and nile. I have detailed the comparison in this github repository. Several aspects are treated:InstallationProject initializationCompilationUnit testingAssertionsMockingDebuggingDeploymentPerformancesAnd the winner is…For the more impatient o...
We onboard devs to the Starknet ecosystem. Our discord : https://discord.gg/onlydust To create Stars, you need Only Dust.
Demystifying StarkNet accounts
IntroductionWhen trying StarkNet for the first time, it’s easy to go through the account setup without paying much attention to it. The documentation just says:Unlike Ethereum, which distinguishes between Externally Owned Accounts (EOA) and contracts, StarkNet doesn’t have this distinction. Instead, an account is represented by a deployed contract that defines the account’s logic — most notably the signature scheme that controls who can issue transactions from it.Then, you are invited to chos...
SOLID cairo - OOP-like pattern
When I learn a new language, my first focus is to build SOLID components while leveraging the feature of this new language. In this article, I would like to present a new convention we at OnlyDust are adopting with regards to cairo development. This new kind of architecture feels like object-oriented programming in a way and leverage several cairo features like:implicit parametersstructsnamespacesFollowing OpenZeppelin’s recommendations about extensibility, we aims at building nice modules th...
protostar vs nile
When starting a new project in a new programming language, there is always this question that is raised.Which framework should I choose ?For Starknet projects, there are especially 2 new frameworks I have been trying and would like to compare: protostar and nile. I have detailed the comparison in this github repository. Several aspects are treated:InstallationProject initializationCompilationUnit testingAssertionsMockingDebuggingDeploymentPerformancesAnd the winner is…For the more impatient o...
We onboard devs to the Starknet ecosystem. Our discord : https://discord.gg/onlydust To create Stars, you need Only Dust.
Share Dialog
Share Dialog
Subscribe to Only Dust
Subscribe to Only Dust
To help it happen there is a lot to do: create communities, involve companies, create some kind of on-chain platform for missions to be posted on. That’s a lot to do, too much for one sprint or even one year. So we decided to start small, to find quick wins that can already greatly improve contribution.
A good way to achieve this is to create a standard of labels for contributions on Github. If all repositories that are open to external contribution adopt it, it will be much more easy to identify, regroup and communicate their needs to potential contributors.
So what to put in this standard, from a potential contributor point of view:
first the obvious, I want to know what type of contribution it is (feature, documentation, refactor, fix, test)
then I want to be able to filter by the amount of time I’m willing to invest in this contribution (up to one day, one week or multiple weeks)
also I could use some information about the degree of complexity the contribution require (can anybody do it or do you have to be a PHD in the area to solve the problem, because I don’t have one 😉)
and last, but not least, I want to know about the amount of context which is required to have before I can start my work (is the contribution an isolated standalone or is it deeply intricated with the rest of the codebase)
And of course we should also have some kind of agreement about the way we talk about the state of a contribution (to do, doing, waiting for review, done).
An adoption of this standard will allow projects to self declare their open contribution and have them handled programmatically by the OnlyDust platform.
We created a first draft of this standard that you can find here: https://github.com/onlydustxyz/github-contribution-labels
And, because a standard only make sense if it is discussed and agreed upon by different groups of people, we highly encourage you to criticize it and make some improvement proposals.
Our discord is here: https://discord.gg/r3Abf2f5
Apes strong together !
To help it happen there is a lot to do: create communities, involve companies, create some kind of on-chain platform for missions to be posted on. That’s a lot to do, too much for one sprint or even one year. So we decided to start small, to find quick wins that can already greatly improve contribution.
A good way to achieve this is to create a standard of labels for contributions on Github. If all repositories that are open to external contribution adopt it, it will be much more easy to identify, regroup and communicate their needs to potential contributors.
So what to put in this standard, from a potential contributor point of view:
first the obvious, I want to know what type of contribution it is (feature, documentation, refactor, fix, test)
then I want to be able to filter by the amount of time I’m willing to invest in this contribution (up to one day, one week or multiple weeks)
also I could use some information about the degree of complexity the contribution require (can anybody do it or do you have to be a PHD in the area to solve the problem, because I don’t have one 😉)
and last, but not least, I want to know about the amount of context which is required to have before I can start my work (is the contribution an isolated standalone or is it deeply intricated with the rest of the codebase)
And of course we should also have some kind of agreement about the way we talk about the state of a contribution (to do, doing, waiting for review, done).
An adoption of this standard will allow projects to self declare their open contribution and have them handled programmatically by the OnlyDust platform.
We created a first draft of this standard that you can find here: https://github.com/onlydustxyz/github-contribution-labels
And, because a standard only make sense if it is discussed and agreed upon by different groups of people, we highly encourage you to criticize it and make some improvement proposals.
Our discord is here: https://discord.gg/r3Abf2f5
Apes strong together !
<100 subscribers
<100 subscribers
No activity yet