on host, not docker, if host is ubuntu 22.04:
cargo build --release --features=skip-extrinsic-filtering
docker setup for worker build
https://github.com/integritee-network/integritee-dev/tree/main/worker
docker run --name integritee-dev-worker-and-node -it -p 9944-9999:9944-9999 -v $(pwd):/home/ubuntu/worker -v $(pwd)/../integritee-node:/home/ubuntu/integritee-node -e MYUID=$(id -u) -e MYGUID=$(id -g) integritee/integritee-dev:0.2.2 /bin/bash
cd integritee-node
- Transfer PAS privately Our Incognitee testnet allows you to transfer PAS privately (Paseo relay chain native token). We will guide you through the process of creating a wallet, obtaining PAS and transferring with privacy. The very same process will be possible with DOT/KSM and even other fungible assets on the Asset Hubs once we release the productive sidechains. At this early stage we only provide command line tools and we assume you know your way around docker or linux. Stay tuned for a web UI for a clickable version of this tutorial. This tutorial will take you through all steps sketched in the following diagram: paseo-incognitee-test-flow.drawio setup
brenzi changed a year agoView mode
- My name is Alain Brenzikofer (github @brenzi). I am requesting to join the Polkadot Fellowship. My primary contributions since 2018 have been to Encointer which has become a system chain of Kusama in Dec 2021 My public Address is DOT: 12brenJreRTd6XsBMo3Ptu5VMUUycC53ipDxUy9Mvb4L1s1q KSM: EBBAmPfR1D5Qeg7AroSehcLeSmZiZL66hLDiLRxrJFJaft6 disclaimer
- you have an sgxmachine set up which can run your worker build in HW mode (can be debug mode, no production license required) assuming your *sgxmachine runs ubuntu 22.04 setup integritee testnet collator Check which version of the collator is currently running on Rococo: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo.api.integritee.network#/explorer In the top right corner, it says: Integritee Collator v1.5.40 On the sgxmachine, do the following:
- Encointer has innovated community currencies with its secure and decentralized sybil-defense protocol, laying the foundation for a brighter future with basic income. Field-tested with several hundred users, this protocol, known as Encointer LoCo, has proven its capabilities in pilot communities like the Leu community in Zurich. With new products, Encointer will not only benefit Kusama as a laboratory for personhood and local community currencies. It will benefit Polkadot directly as well: The faucet will be useful for new token launches, i.e. on Polimec The personhood oracle will be useful for privacy-preserving sybil-resilience for projects like KILT, subsocial as well as many others BeeDance will foster community engagement at meetups and events everywhere around the world and could become a massively useful tool for Polkadot ambassadors So far, expenses have mainly been funded by the KSM treasury. Starting with September 2023, the team proposes to be funded by the Polkadot treasury on the grounds that Polkadot and its parachains benefit from new products to be released in the next few months. See milestones.
- How Encointer can grow to deliver proof-of-personhood on a global level within a few months and serve as a potentially secure-enough basis for sybil-resilient quadratic voting. What is a POAP and why it isn't a proof of personhood A POAP Proof of attendance is commonly understood as a proof that you attended a physical or virtual event which is issued by the event organizer. Usually, attendants scan a QR code shown to the audience and claim an NFT. While this may be fun for collectors, there's so much more that could be done, would the POAP protocol be harder to game: Participants can claim multiple times for themselves or forward a picture of the qr code to their friends at home who can then claim the NFT as well. Therefore, as soon as POAs should be with something, the protocol will break. Shortcomings of POAP: people who aren't there can claim a POA with just one person leaking the QR code and no one even notices this attack if small-scale with respect to the audience. the event organizer is the single trusted authority to issue the POA
- Integritee has developed TEE-validated L2 sidechains and has demonstrated private transactions based on its SDK in Q1 2022. One year has passed and we are now close to providing this technology to all substrate-based L1 chains, as well as to the Polkadot and Kusama relay chains – without the need to change one line of code on L1 runtimes. Pre-Discussion for Treasury Proposal Integritee aims to propose privacy sidechains to Statemine and Statemint to the DOT/KSM treasuries. A blog post (TODO: LINK) has been published to seek feedback from a wide audience and here on this repost on Polkassembly, we'd like to offer room for discussion before we take further action on the treasury proposal. Introduction The Dotsama ecosystem is highly transparent nowadays. The information, who is transacting with whom and how much, who you nominate, how you vote, and whom you elect to the council is publicly visible to anyone. While this does have its advantages when it comes to accountability, it is not a sound setup for everyday actions. The inherent linkability of everything that happens on transparent blockchains prohibits a wide range of use cases – or would you really want to disclose personal identity attributes on i.e. KILT in order to gain access to a certain service, if you know that this information can be linked back to your original DOT presale participation and trading history? Or your votes on a controversial topic on any other parachain, linkable through XCM? Follow the money and you’ll be able to retrieve a lot of personal sensitive information way beyond token balances.
- Basic Units for Kusama: https://github.com/paritytech/polkadot/blob/3fbf6e4698e6abcc621095c8bbeefe37f70568be/runtime/kusama/constants/src/lib.rs#L26-L32 CENTS: 333uKSM (was 33.3 uKSM) QUID: 33.3mKSM (was 3.33 mKSM) GRAND: 33.3 KSM (was 3.33 KSM) Treasury Spend Origins Origins https://github.com/paritytech/polkadot/blob/b984c40cc5217eda68f630e329320dc26578a0bc/runtime/kusama/src/governance/origins.rs#L55-L60
- This report covers activities for June to and including September 2022 which have predominantly been financed by the Kusama Treasury. As mentioned in our proposal, there are no fixed deliverables within a fixed timeframe defined for acceptance of our work. We stated our plans and budgets and here we report about how the funds have been used and what has been achieved. For acceptance, we ask reviewers to judge whether the funds have been used on target and efficiently so. Encointer Protocol A critical bug has been fixed with a runtime upgrade to v8 on Aug 15th. With the same upgrade, we also improved the protocol based on the first field experience in Zurich. Noteworthy PRs The following changes will be deployed with our upcoming parachain runtime upgrade, if approved by the Kusama governance. 254 allow to update/cancel registration for ceremonies. This helps maintaining reputation as a no-show will be punished by downgrading reputation status 255 lift permissioning for non-destructive actions on Testnet Gesell. This way, anyone can run through our tutorials without intervention from the team. This helps with scaling up onboarding of new communities
- More context here: form a community Shares the core values of Encointer equal opportunity for all humans, regardless of gender, race, citizenship status, age, sexual preferences support local economy Trustwothy Bootstrappers are the trusted setups of a community
- Due to a human error, integritee's sudo account has been reaped and the team can no longer operate its parachain nor migrate its solochain to the parachain. This proposal aims to restore the integritee parachain by setting a new genesis head. what happened Integritee launched its parachain with a shell runtime which features basic pallets like sudo, balances, vesting. This runtime has an extrinsic filter in place, so only sudo is allowed to send extrinsics The sudo account initially was endowed with 10M TEER, the total supply planned. Because integritee launched its mainnet as a solochain before onboarding as a parachain, the team wanted to destroy the TEER tokens on its parachain before migrating its solochain state to the parachain. This should avoid confusion because we'd no longer have 10M TEER on solo plus 10M TEER on para. It was planned to leave 10 TEER for sudo, to be able to pay fees. Due to a human error, the sudo call balances.setBalance was called with the argument 10 instead of 10_000_000_000_000, so the account went below the existential deposit and was reaped.
