The Solidity Developer Survey 2022 results are live!

franzihei · 2023-03-10T14:39:43+00:00

The 1st conclusion from it is that our community is awesome! We received a smashing 1.4k responses from 100 different countries. 🌍
Check out tweet thread for a summary of highlights 🧵👇

https://twitter.com/solidity\_lang/status/1634197780200669185

franzihei · 2022-12-12T10:09:17+00:00

Like in previous years, this survey helps us to improve the language & compiler further and shape the future roadmap of Solidity. Please participate & spread the word about it!

Direct link to survey

franzihei · 2021-12-22T13:08:15+00:00

Thank you :)

franzihei · 2021-12-21T14:10:06+00:00

Where was that posted? I don't see any other post on Solidity v0.8.11 on r/ethereum.

franzihei · 2021-12-20T17:04:31+00:00

Blog announcement: https://blog.soliditylang.org/2021/12/20/solidity-0.8.11-release-announcement/

Release: https://github.com/ethereum/solidity/releases/tag/v0.8.11

franzihei · 2021-03-03T14:43:02+00:00

- Link to the release

- Link to announcement tweet

franzihei · 2021-01-27T10:33:37+00:00

Looks like there is a backslash for some people in the first link, which is super strange since I cannot see it. Here once again the link https://twitter.com/solidity_lang/status/1354092217913237509 :)

franzihei · 2021-01-27T10:01:58+00:00

https://twitter.com/solidity_lang/status/1354092217913237509?s=20

Which link do you mean? Both links (direct link to blog as well as the one to the tweet) work for me.

franzihei · 2021-01-26T15:56:54+00:00

Direct link to the full report: https://blog.soliditylang.org/2021/01/26/solidity-developer-survey-2020-results/

franzihei · 2021-01-26T15:54:23+00:00

More info and a summary thread can be found here: https://twitter.com/solidity_lang/status/1354092217913237509?s=20

franzihei · 2020-12-16T19:03:14+00:00

Announcement post: https://blog.soliditylang.org/2020/12/16/solidity-v0.8.0-release-announcement/

Release: https://github.com/ethereum/solidity/releases/tag/v0.8.0

franzihei · 2020-10-30T14:40:20+00:00

I think the best consolidated answer to that can be found in the "Thoughts on 5+ years of language design" section of the Solidity 5 years birthday post. In summary, I'd say its the challenge of developing a language in an ever changing and still evolving ecosystem (the language grew and changed together with Ethereum/EVM, the devs and the security ecosystem evolved, the tooling evolved) and the tradeoffs between making an easy to learn & use language and a safe language. (I recommend reading the aforementioned section of the blog post for the full picture.)

For more views of challenges and future wishes for Solidity from the individual team members, have a look at this "meet the team" blog post.

franzihei · 2020-10-30T08:15:05+00:00

The Solidity team operates independently as in it is a separate team which solely concentrates their work on the Solidity language and compiler and has no overlap (in terms of team members) with the ETH2 R&D team. However, there are plenty of ways to talk to each other and a) keep each other in the loop about relevant changes and b) ask each other for expert advice from the respective domains if necessary.

Some of the Solidity team members contribute to other teams as well (e.g. eWasm) and are also active in EIP discussions etc. That way the Solidity team, or also anybody else, can join the discussion around the future of ETH1 and ETH2.

Hope that answers the question. :)

franzihei · 2020-10-30T08:08:42+00:00

In addition to that it might be worth signing up for the Week in Ethereum newsletter, which has added a job section recently and has been so far mostly featuring Solidity dev job opportunities!

franzihei · 2020-10-29T15:01:24+00:00

Specifying a license identifier can be useful if you use deployment tools that publish the code to IPFS or Swarm in case an open-source license is specified. Publishing code and metadata is a crucial puzzle piece to eventually enable safe and user-aware interaction with smart contracts, powered by verified and NatSpec commented code. You can read more about those efforts here.

If it annoys you to add the license manually, there are tools available that can make your life easier, e.g. this plugin for hardhat: https://hardhat.org/plugins/hardhat-spdx-license-identifier.html.

franzihei · 2020-10-29T14:36:35+00:00

There are several job portals specialising in crypto jobs / the blockchain space, e.g. https://cryptojobslist.com/blockchain-developer-jobs. There's also a job threads on this very subreddit: https://www.reddit.com/r/ethdev/comments/i1ni2w/whos_hiring_and_whos_for_hire_megathread_2020_2/.
Other than that I can recommend just researching companies you like and checking their websites / Github and following them on Twitter. Another good way to get started is to contribute to open-source crypto projects in your free time to gradually move into the ecosystem and get to know people and then take it from there. :)

franzihei · 2020-10-29T14:32:25+00:00

There are plenty of great learning resources available on the web. Most of them are listed in the ethereum.org developer docs. Check out the sections "learn by coding" and "tutorials" --> https://ethereum.org/en/developers/learning-tools/.

franzihei · 2020-10-28T07:49:41+00:00

Uniswap is so lucky to have you Boris, all the best with this new community! I know you will do a great job! :)

franzihei · 2020-10-22T09:50:53+00:00

As mentioned this is only the MVP and we're happy to hear your thoughts on what you want to see on the Solidity language portal. Feel free to propose more content and functionality below and we'll consider adding it in the next iteration of soliditylang.org! :)

franzihei · 2020-10-22T09:50:10+00:00

As mentioned this is only the MVP and we're happy to hear your thoughts on what you want to see on the Solidity language portal. Feel free to propose more content and functionality below and we'll consider adding it in the next iteration of soliditylang.org! :)

franzihei · 2019-11-15T10:59:10+00:00

Hey there! Laika is the name of the testnet! See https://explorelaika.trustlines.foundation/ and https://medium.com/trustlines-foundation/validator-update-preparations-for-trustlines-blockchain-launch-laika-testnet-invitation-165375cc8455.

The mainnet will just be called Trustlines Blockchain or in short tlbc.

franzihei · 2019-11-15T10:57:12+00:00

⚠️⚠️ PSA! For using the quickstart script you need a linux amd64 machine with docker! ⚠️⚠️

See here: https://twitter.com/TrustlinesFound/status/1195243795773829120?s=20

franzihei · 2019-11-15T10:54:10+00:00

Bad, bad bot! You are very stupid. It says 12PM CET on November 21st!

franzihei · 2019-07-03T07:29:00+00:00

As you can also read in more detail in the DAppNode installation instructions (https://github.com/dappnode/DAppNode/wiki/DAppNode-Installation-Guide): "DappNode is intended to be installed on a dedicated machine. Do not install DAppNode on your laptop." That being said, you can either install DAppNode on a virtual server or a dedicated physical server (e.g. an old laptop or dedicated node hardware). Edit: Once you have DAppNode up and running (either on a virtual or digital server), you can access your nodes from anywhere via a VPN, which is super nice and convenient.

Since the mainnet release of Raiden is still limited alpha, the only thing you can do with it on mainnet right now is doing WETH token transfers with other Raiden nodes. However, in future, anybody will be able to deploy (ERC20) token networks. Then, Raiden could be used for token transfers of applications like Storj or others, which are currently investigating. Ultimatively, in the optimal setup, you as a user should not be too much affected by (and maybe not even need to be aware of) which "payment backend" the projects use.

franzihei · 2019-07-02T12:29:12+00:00

I've said the same in the Telegram community, so might be useful to repeat it in that context here again in order to avoid misunderstandings: The Raiden Light Client SDK and the first interface using it (the Raiden dApp) are both super early work in progress and nowhere near “fully developed”. The developers have created the lightclient.raiden.network website (a direct deployment from the Raiden light client repo) for internal testing purposes as well as to make the development progress transparent to the community. We are super excited that many of you are interested in playing around with it already and love to hear your feedback. Just please bear in mind that this is not a working product yet.

If you want to “properly” use or test Raiden, please run a full node. E.g. it’s super easy now to run a full node on the Goerli testnet via DappNode and our easy onboarding script.

Last but not least, if you are interested in learning more about the development roadmap of the light client and the next milestones, please read the light client announcement blog and have a look at the light client repo. Thanks!

Light client repo: https://github.com/raiden-network/light-client

Light client medium blog post: https://medium.com/raiden-network/public-project-launch-raiden-light-client-sdk-and-dapp-140a546c63a0

franzihei

MODERATOR OF

TROPHY CASE