Короткая версия на примерах Пример с транзакцией добавления ликвидности. Это вызов функции addLiquidity в контракте PancakeSwap Router v2 (0x10ED..): Пример с транзакцией, разрешающей пользоваться токеном в нашем Сейфе третьему лицу/контракту. Вызывается функция approve (часть стандарта ERC20) у контракта токена (в данном случае это Cake-LP токен по адресу 0xD1718..) с параметрами sender = 0xa5f8.. и длинным value. Этой транзакцией мы разрешаем аккаунту 0xa5f8.. пользоваться нашими токенами Cake-LP в размере value (значение указано в копейках, если поделить это значение на 10^18 увидим сумму в токенах): Подробная версия :::info Это не техническая документация, тут много упрощений для понятности. :::

This is a rolling document for General Circle Tactical and Governance calls. Please add your reports, tensions and/or questions below so you don’t forget by the time we have the call! 💁 What is the LeapDAO General Circle? Tactical: the call is every Monday at 10:30 UTC on jitsi. Find more calls on the LeapDAO community calendar or in slack.

Current purpose: Help collectives of people to collaborate on things they care about and achieve sovereignty in a non-violent and fulfilling way. Current strategies: We work as an async holacratic organization driven by active and honest people We are evaluating Plasma as a L2 solution to fast, inexpensive and secure way for running Dapps in the Ethereum ecosystem We are not competing but rather open towards & actively contacting new collaboratives and initiatives with a common purpose We dogfood all the ideas

21.11.2019 — Got 57,425 DAI tx 24.04.2020 — Balance left 24,454 DAI Spending breakdown Core Development 20000 DAI Network operations 1928 DAI

Let's review building blocks of Holacracy starting from the very beginning. The Purpose Group of people (Partners) gather and decide on a shared goal they want to work on together. This goal becomes a purpose of the organization (Purpose of the Super Circle). It is like declaring "We all here together because we care about the thing we've written as the Purpose and we want to make it reality". Expectations instead of prescriptions Ok, we've agreed on where we are moving to. Now what?

Proposing changes to Bounty Process: See here: https://github.com/leapdao/meta/pull/226/ Outline: extracted Bounty Specification from Bounty Policy into separate doc https://github.com/leapdao/meta/tree/master/playbook/bounty.md (not yet merged) bounty should address Role purpose, not Project purpose added Gardener/Worker/Reviewer descriptions from Onboarding wiki added expectations for Gardener/Worker/Reviewer

16 March 12:18 UTC Period submission on height 227424 has failed by validator 2. Reason is unclear — tx was dropped out of the mempool. We have a checkBridge mechanism to recover from such an error, it was expected to fire on a next period submission. Blocks were still produced at this point, only the period sumission was missing 16 March 13:18 UTC New period proposal was created on height 227456. checkBridge successfully figured out a missing period submission and assigned validator 1 to resubmit it. Period was submitted with tx hash 0x13ebe8cf83c6657b0ee3087d3a6bd19948f6186d193e33156bba04250c131b42. Problem checkBridge failed to detect period submission was mined just right and kept waiting on it stopping block production.

# Making LeapDAO process more async ## Problems 1 . Chat (Slack) is a focal point for most of the decision making and information sharing. This forces people to spend a lot of time on the chat catching up with conversations. Otherwise, people lose track on what's going on and experience FOMO and sense of exclusion from decision making process. 2 . Information is lost easily and there is no well-known way how to find it. E.g. how to see which payout requests need to be processed, how to see whi

# Simple Summary This policy allows to write out rewards to complete required tasks. Completed tasks are payed by the Escrow council to the claiming member. # How to create a new bounty? 1. Create an issue with bounty description and a bounty tag in an appropriate repository. If the bounty spans across multiple repositories, consider splitting it in a smaller per-repo bounties if possible. 2. Submit proposal via the bounty form: http://bounty.leapdao.org/viewform 3. Add the bounty to the b

# LeapDAO Purpose 3.0 Current purpose: > We are building a fast, inexpensive and secure way for running Dapps in the Ethereum ecosystem. We want to work as a holacratic organization driven by active and honest people. Organization that is open for anyone and empowering people to propose changes, bring them to reality and get rewarded. We believe in decentralization and that technology can solve coordination problems plaguing humanity. Current strategies: > A decentralized adaptive organization

# Propose missing things and get paid 100 DAI for each We want to identify a missing pieces in Plasma Leap roadmap. ## Status Effective till 01.01.2020. Budget left: 1900 DAI ## The offer - Create a Github issue describing the problem (see applicable repos and problem types) - Respond to clarifying questions (if any) - Get the payout from Dev Circle Multisig of at least 100 DAI for each item. See Payout section below. Offer is limited with 2000 DAI or till the end of the year ## Applicable

# Dev Circle ## Intro LeapDAO is an adaptive organization with the purpose to scale Ethereum Dapps without compromising on security. "To scale" here means faster and less expensive Dapps execution. The current LeapDAO's strategy to achieve that is to develop, launch and foster a general purpose Plasma chain (Leap Network). From the many flavours of Plasma frameworks, we chose More Viable Plasma and Plasma Leap. More Viable Plasma (MVP) design covers simple transfer transactions on plasma chai

# Double-crossing Salary policy in Dev Circle > Dev Circle Governance proposal Proposing a new policy to use in Dev Circle instead of Salary Policy: [Subsidized Crew (aka "Dev Multisig Heist")](/Uvk8o8rJTgGmdQXJYgkHMA) The idea is to provide a subsidy to peeps willing to work full time on the project, but worrying about the basic needs. The subsidy is supposed to limit a downside for the working peep, while the upside is still unlimited (ahem, to the limit of total amount of money in multisi

# Subsidized Crew (aka "Dev Multisig Heist") ## How to get in You must be invited in public by one of the Dev Circle role holders: *Inviter: @username your skills are required for a job* *You: You son of a bitch. I'm in.* That's it, you're in. ## What's The Job - Sneak in a #devcrew channel on Slack. - Work on Dev Circle bounties full time. Deliver first, review and garden second. - Report your progress daily to a standup bot from #devcrew channel. ## The thing Crew members can claim 2

# Ops Circle Governance proposals 1. Facilitator election 2. Secretary election 3. Change **Mainnet Commander** Role - New **Accountability:** - investigate and resolve issues with mainnet - create post-mortems for each mainnet issue and post it to #mainnet - collecting mainnet block tax monthly - reporting on the amount of block tax collected - keeping community validator funded for period submissions - monitoring no period submissions missing 4. Chan

# Define a new bounty All the following steps MUST be executed in order for bounty to be defined: - create a Github issue with: - description («why it is needed?») - scope («what needs to be done?») - deliverables («what are the artifacts to be delivered in result?») - "Gain for the project" («how is the bounty aligned with the funding circle's purpose and strategies?») - "Funded by" section («which circle/multisig pays the bounty?») - "bounty" label - size label (o

# Postmortem for incomplete LEAP validator reward claim for 29 June till 28 Sept period On Sept 28 @kosta claimed a period rewards from a single Leap Mainnet validator for block interval 8047181 — 8637840 (roughly June 29th — Sept 28th)[[1]](https://leapdao.slack.com/archives/C75C00YJD/p1569682999002100). As result 785002 LEAP tokens were claimed and distributed proportionally to team reputation [[2]](https://leapdao.slack.com/archives/C75C00YJD/p1569859711003000). ## Problem However, on Aug

# General Governance proposals buffer 3. **new domains:** - **validator signer key** domain. - use key in node or for tax withdrawal. - **calendar** domain. - share write access to calendar. 3. **new roles**:

# Dev Circle Governance proposals 1. Add **AWS Access Holder** Role - **Purpose:** accessible AWS account - **Domains:** AWS (IAM & SSH) users and access tokens - **Accountabilities:** - creating limited access accounts for newly onboarded people upon request - creating/providing credentials for infrastructure needs (Travis) - deleting accounts upon offboarding 2.

# Planet A @ EthBerlin2 and CCCamp 2019 — Postmortem ## Kosta Direct feedback from the people: - 👎no instructions in the app itself. Will be good to have a game explainer right in the app. - 👍many people liked the idea (once it was explained) - 💡would be good to know how you can spend GOE right from app e.g. have a list of merch with prices. Or even a marketplace for small digital goodies like Kudos. Observed behaviour: - all the people had no clue they can spend their GOE anyhow - peopl