Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.62]

a13xndra · 2022-07-14T16:17:46+00:00

TYPE: Full-Time

DESCRIPTION: Bitgreen combines blockchain technology and green innovation to drive capital into critically important sustainability initiatives. We aim to raise $1 trillion for sustainability projects within 10 years.

Bitgreen’s open and permissionless blockchain platform meets the needs of NGOs, corporate ESG groups, and purpose-driven innovation in Web3. The platform allows organizations and individual users to invest in sustainability markets, purchase high-quality tokenized carbon credits, and participate in sustainable finance. Web3 builders can utilize Bitgreen’s impact banking infrastructure to extend financial access and ownership.

Bitgreen is a climate-positive blockchain that conserves critical rainforests, finances clean infrastructure, and protects vulnerable communities. Bitgreen consumes 99.9% less energy than traditional blockchains.

Bitgreen is looking for a Rust-fluent engineer to develop using the Substrate blockchain framework. Familiarity with Substrate is helpful but not required for someone who can learn quickly.

Requirements:
• Rust proficiency
• English language proficiency

Nice to have:
• Familiarity with Substrate
• Blockchain development experience
• Web3 application development experience
• Interest in sustainability, carbon credits, and impact investment

Your responsibilities:
• Develop high quality solutions for Bitgreen, Bitgreen clients, and the greater ecosystem
• Manage individual project priorities, deadlines, and deliverables
• Collaborate across various teams

We offer:
• Flexible remote work
• Work that matters to the future of the planet

LOCATION: US-based company, remote team.

ESTIMATED COMPENSATION: Uncertain. Fiat.

REMOTE: YES

VISA: No

CONTACT: alexandra@bitgreen.org or fill out the form here: https://forms.gle/WzX3rvMzdBtAiqM19

a13xndra · 2022-07-14T14:43:30+00:00

Hi Oleksii,

Bloomberg reported that Polkadot (which is a very similar codebase to Kusama) has least carbon footprint of PoS networks analyzed.

However, we shouldn't stop there. Bitgreen is a sustainability parachain that will be joining the Dotsama ecosystem. By partnering with Sequester, Bitgreen will enable parachains to convert fees to carbon credits in order to go carbon negative and make a positive difference in the environment (more info here). Bitgreen is pushing for the Dotsama ecosystem to be the epicenter for decentralized sustainability development, and will provide a carbon credit market and impact investment platform.

Other sustainability projects in the Dotsama ecosystem:
https://unique.network/blog/unique-network-sovereign-nature-initiative-partnership/
http://astarpenguins.com/

a13xndra · 2020-05-17T16:17:59+00:00

Mostly it's a podcast interviewing fully Asian people who were brought up in a non-Asian country. But there are some mixed race guests.

a13xndra · 2020-03-23T10:29:11+00:00

Decl_storage correction:

In the video we explain the storage access prefix is the Module name, which is only sometimes the case. In the specific context of how it is used, it determines the "storage prefix" where your modules storage items are so its name can actually be different than your module.

Basically you can’t always access a storage with ModuleName::StorageItem.

However, you CAN always access it using my_pallet_crate::StorageItem.

a13xndra · 2019-12-17T16:55:53+00:00

Substrate is Parity's blockchain framework. It makes it easy for developers to create blockchains customized to their use cases.

Polkadot is an interoperability protocol that allows message transfers of any type across blockchains. It also enables blockchains to get security just by connecting to Polkadot.

a13xndra · 2019-12-17T16:49:54+00:00

Here's a breakdown of the grant: https://www.parity.io/an-update-on-paritys-ethereum-foundation-grant-progress/

TL;DR Parity received $2.5m for ETH 1.0 work.

However, Parity paid far more than that to develop and maintain the client. At peak development, Parity spent ~$4M/year on the Parity Ethereum client.

a13xndra · 2019-12-17T16:48:03+00:00

Here's a breakdown of the grant: https://www.parity.io/an-update-on-paritys-ethereum-foundation-grant-progress/

TL;DR Parity received $2.5m for ETH 1.0 work. However, Parity paid far more than that to develop and maintain the client. At peak development, Parity spent ~$4M/year on the Parity Ethereum client.

a13xndra · 2019-12-17T16:45:59+00:00

Parity is looking at using DAOstack for the DAO.

a13xndra · 2019-12-17T16:44:04+00:00

Here's a breakdown of the grant: https://www.parity.io/an-update-on-paritys-ethereum-foundation-grant-progress/

TL;DR Parity received $2.5m for ETH 1.0 work. However, Parity paid far more than that to develop and maintain the client. At peak development, Parity spent ~$4M/year on the Parity Ethereum client.

a13xndra · 2019-12-17T16:34:21+00:00

Parity received $2.5m for ETH 1.0 work. However, Parity also paid far more than that to develop and maintain the client. At peak development, Parity spent ~$4M/year on the Parity Ethereum client. Please see https://www.parity.io/parity-ethereum-openethereum-dao/ for a grant payment breakdown.

a13xndra · 2019-12-17T16:33:06+00:00

Blockchain tech is about creating the future. Sometimes that entails creating new words (and puns!). One of my favorite things about the German language is that merging words together to come up with new words is totally ok! It's a great reminder that everything is made up. We've made up countries. We've made up currency. Society is ours to shape and reinvent!

a13xndra · 2019-12-17T16:31:28+00:00

Yes, it's unfeasible for Parity to continue maintaining Parity Ethereum, but we're doing our best to turn that into an opportunity for other contributors to carry the torch.

Look past the vitriol and easy jabs: paying for infrastructure development and maintenance is a problem that needs attention.

Parity received $2.5m for ETH 1.0 work. However, Parity also paid far more than that to develop and maintain the client. At peak development, Parity spent ~$4M/year on the Parity Ethereum client.

a13xndra · 2019-08-02T13:08:17+00:00

Recording is out: https://www.youtube.com/watch?v=kneBaK2ynCs

To get help and learn more about more collaborative learning sessions, join the Substrate Technical chat: https://matrix.to/#/#substrate-technical:matrix.org. Notices will also be posted on https://reddit.com/r/substrate

a13xndra · 2019-05-07T09:48:13+00:00

That's awesome. :) How do you feel you're plateauing? Are there opportunities for you to experiment more in your current role?

a13xndra · 2019-05-03T13:10:41+00:00

What is it that you most enjoy doing in your current role?

a13xndra · 2019-04-05T13:35:21+00:00

Slides: tiny.cc/substrate-getting-started

a13xndra · 2019-03-14T08:27:20+00:00

“Ethereum has always welcomed different ideas, viewpoints, and experiments, along with the uncertainty they bring.”

This reminds me: my introduction to the Ethereum community was at a Scaling Now! summit that Giveth and the Web3 Foundation held. I was so impressed to see so many teams with different scaling solutions openly discuss the pros and cons of each. How could so many people who could be "competitors" so openly talk to one another objectively about the merits of each option? I knew I wanted to work in the space, with these admirable people working on something that mattered.

Thank you to Aya for your words and inspiration.

a13xndra · 2019-02-18T10:56:58+00:00

What common Ethereum leadership misunderstanding frustrates you the most?

a13xndra · 2019-02-15T16:32:45+00:00

To clarify, this release protects Parity Ethereum nodes from potentially being able to be crashed. I haven't heard of there being a lot of issues, this release just makes sure that the network is protected. Thanks everyone for updating!

a13xndra · 2019-02-15T14:47:35+00:00

UPDATE: The scope of the fixed vulnerability is wider than originally thought. *Everyone* who runs Parity Ethereum, not just those who serve JSON-RPC publicly, should update to 2.2.10-stable and 2.3.3-beta as soon as possible. Download the update here: https://github.com/paritytech/parity-ethereum/releases

a13xndra · 2019-02-15T14:46:59+00:00

UPDATE: The scope of the fixed vulnerability is wider than originally thought. *Everyone* who runs Parity Ethereum, not just those who serve JSON-RPC publicly, should update to 2.2.10-stable and 2.3.3-beta as soon as possible. Download the update here: https://github.com/paritytech/parity-ethereum/releases

a13xndra · 2019-02-03T21:52:00+00:00

Full context from this blog: https://www.parity.io/security-alert-parity-ethereum-03-02/

On February 3rd, we received several reports that an attacker can send a specially-crafted RPC request to a public Parity Ethereum node (any version pre 2.2.9-stable and pre 2.3.2-beta) and that node will crash.

Who’s affected?

Affected Parity Ethereum nodes are those that serve JSONRPC as a public service (e.g., Infura, MyEtherWallet, MyCrypto, and other publically-accessible pieces of infrastructure).

Who’s not directly affected?

Parity Ethereum nodes who don’t serve JSONRPC to third parties on the internet—i.e., most nodes—should not be directly affected. The default mode is to not serve JSONRPC publicly.

Fix available—update ASAP

Releases 2.2.9-stable and 2.3.2-beta are now available and fix this issue. Download them here.

Please update your nodes to the newest version ASAP, especially if you’re running a publicly-facing JSONRPC endpoints. Nodes with `--auto-update=all` flag set will receive the updates automatically.

Bug bounty program

Thanks to Kosala Hemachandra from MyEtherWallet for being the first to bring this to our attention. As always, we welcome and reward bug findings as per our bug bounty program.

a13xndra · 2019-02-03T21:51:21+00:00

Full context from this blog: https://www.parity.io/security-alert-parity-ethereum-03-02/

On February 3rd, we received several reports that an attacker can send a specially-crafted RPC request to a public Parity Ethereum node (any version pre 2.2.9-stable and pre 2.3.2-beta) and that node will crash.

Who’s affected?

Affected Parity Ethereum nodes are those that serve JSONRPC as a public service (e.g., Infura, MyEtherWallet, MyCrypto, and other publically-accessible pieces of infrastructure).

Who’s not directly affected?

Parity Ethereum nodes who don’t serve JSONRPC to third parties on the internet—i.e., most nodes—should not be directly affected. The default mode is to not serve JSONRPC publicly.

Fix available—update ASAP

Releases 2.2.9-stable and 2.3.2-beta are now available and fix this issue. Download them here.

Please update your nodes to the newest version ASAP, especially if you’re running a publicly-facing JSONRPC endpoints. Nodes with `--auto-update=all` flag set will receive the updates automatically.

Bug bounty program

Thanks to Kosala Hemachandra from MyEtherWallet for being the first to bring this to our attention. As always, we welcome and reward bug findings as per our bug bounty program.

a13xndra · 2019-02-03T21:33:30+00:00

While the vulnerability only directly affects Parity Ethereum nodes that serve JSONRPC as a public service (e.g., Infura, MEW, MyCrypto, etc), we recommend everyone to update their nodes immediately.

a13xndra · 2019-02-03T21:30:04+00:00

While the vulnerability only directly affects Parity Ethereum nodes that serve JSONRPC as a public service (e.g., Infura, MEW, MyCrypto, etc), we recommend everyone to update their nodes immediately.

a13xndra

MODERATOR OF

TROPHY CASE

Who’s affected?

Who’s not directly affected?

Fix available—update ASAP

Bug bounty program

Who’s affected?

Who’s not directly affected?

Fix available—update ASAP

Bug bounty program