SubSquare is a governance platform designed for substrate based blockchains, and we have implemented subsquare for khala since Jul 2021. For continuous services to phala community, we request maintenance for phala and khala subsquare integration from 03.2023 to 08.2023.

## Work scope

- Daily devops/monitor work to keep the deployment well running.
- Track and update common dependencies like polkadot api.
- Part of delivered enhanment features
    - Calendar features.
    - UI improvements like menu foldable, cmdk support, etc.
    - Governance data statistics
    - Delegation support.
- Part of development plans
    - User governance activities on profile page.
    - User votes management. User should be able to view the list of democracy votes and manage them.
    - Support users to upload images directly via subsquare editor.
    - Show democracy vote calls for democracy referenda.

## Cost

We request $700 per month for [khala](https://khala.subsquare.io/) and $500 per month for [phala](https://phala.subsquare.io/).

| Item        | Detail            | Cost   |
|-------------|-------------------|--------|
| Khala maintenance | 2023.03 - 2023.08 | $4,200 |
| Phala maintenance | 2023.03 - 2023.08 | $3,000 |
| Total      | $0.124/PHA by EMA7 price on subscan | 58,065 PHA |



proposalId

Maintenance of Subsquare khala and phala integration from 03.2023 to 08.2023

This motion will trigger the runtime upgrade for Khala Network Runtime v1247 with the following major updates:

- Fix the min balance problem which causes GK stuck at Phala Network

For details, please check [here](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.24-3-runtimes-1247)

proposal

Khala Runtime Upgrade v1247 - motion #213

This motion is a retry of:

- [Motion 209](https://khala.subsquare.io/council/motion/209): didn't have enough PHA to create assets
- [Motion 207](https://khala.subsquare.io/council/motion/207): didn't receive enough votes.

## Original Proposal

This motion will first trigger a Transact message on Kusama to open a HRMP request to Picasso Network then register PICA on Khala.

The transact will be performed on Kusama with the following call:

```
0x3c00270800001027000000900100
```

which can be decoded as:

```
hrmp.hrmpInitOpenChannel(
  recipient: 2,087
  proposedMaxCapacity: 1,000
  proposedMaxMessageSize: 102,400
)
```

Phala's sovereign account has already got the enough deposit to open the channels.

PICA registry info is:

```
Picasso PICA: id=15, path=”../Parachain(2087), sym=PICA,dec=12, exePrice=default
```


Open Khala -> Picasso Network HRMP & Register PICA on Khala (3) - motion #212

Dwellir is currently serving the community with a public Phala RPC endpoint service.

This proposal is to cover the costs for the remainder of Q2 2023.

Read the [full proposal here](https://docs.google.com/document/d/1xjjtbd2Zz_tqriz9tNdSBrvlRhe-2U56x4N4fXDsPws/edit?usp=sharing).

The PHA price has been calculated as the average prices over the last 30-days.


Dwellir - Phala Public RPC Endpoint Service (Q2 2023)

This motion will trigger the runtime upgrade for Khala Network Runtime v1246 with the following major updates:

- Fix Khala new worker cannot be registered problem
- Fix Phala message queue txpool sequence checker

For details, please check [here](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.24-3-runtimes-1246)

Khala Runtime Upgrade v1246 - motion #210

This motion is a retry of [Motion 207](https://khala.subsquare.io/council/motion/207) which didn't receive enough votes.

## Original Proposal

This motion will first trigger a Transact message on Kusama to open a HRMP request to Picasso Network then register PICA on Khala.

The transact will be performed on Kusama with the following call:

```
0x3c00270800001027000000900100
```

which can be decoded as:

```
hrmp.hrmpInitOpenChannel(
  recipient: 2,087
  proposedMaxCapacity: 1,000
  proposedMaxMessageSize: 102,400
)
```

Phala's sovereign account has already got the enough deposit to open the channels.

PICA registry info is:

```
Picasso PICA: id=15, path=”../Parachain(2087), sym=PICA,dec=12, exePrice=default
```


Open Khala -> Picasso Network HRMP & Register PICA on Khala (2) - motion #209

This motion will trigger the runtime upgrade for Khala Network Runtime v1245 with the following major updates:

- Better dust processing in Vault. Fixed a bug preventing the withdraw from some vults.
- Node client stability improvements

For details, please check [here](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.24-3-runtimes-1245)

Khala Runtime Upgrade v1245 - motion #208

This motion will first trigger a Transact message on Kusama to open a HRMP request to Picasso Network then register PICA on Khala.

The transact will be performed on Kusama with the following call:

```
0x3c00270800001027000000900100
```

which can be decoded as:

```
hrmp.hrmpInitOpenChannel(
  recipient: 2,087
  proposedMaxCapacity: 1,000
  proposedMaxMessageSize: 102,400
)
```

Phala's sovereign account has already got the enough deposit to open the channels.

PICA registry info is:

```
Picasso PICA: id=15, path=”../Parachain(2087), sym=PICA,dec=12, exePrice=default
```


Open Khala -> Picasso Network HRMP & Register PICA on Khala - motion #207

This motion intends to enable the HRMP channel to InvArch Tinkernet. The proposal was brought to the council and as external referendum for a few times but all the tries were failed, due to either the technical problems and mistakes, or not reaching the voting threshold. In the past voting, there's no strong signal against this proposal.

In the last motion (205) where the proposal didn't pass as a referendum. However the opposition party has never given out a clear reason in public spaces (SubSquare, Discord, and Twitter). Therefore, I proposed this motion to bring it back to the democracy again, hoping it can attract more votes to the referendum to unblock the HRMP integration.

# Original Proposal

This motion will trigger two Transact message on Kusama to accept&send the HRMP request sent from InvArch Tinkernet.

The first transact will be performed on Kusama with the following call:

```
0x3c014d080000
```

which can be decoded as:

```
hrmp.hrmpAcceptOpenChannel(
  sender: 2,125,
)
```

The second transact will be performed on Kusama with the call:

```
0x3c004d080000e803000000900100
```

which can be decoded as:

```
hrmp.hrmpInitOpenChannel(
  recipient: 2,125,
  proposedMaxCapacity: 1,000
  proposedMaxMessageSize: 102,400
)
```


Khala's sovereign account has already got enough deposit to open the channels.

Accept & Open HRMP channel with InvArch Tinkernet (4) - motion #206

[Motion #194](https://khala.subsquare.io/council/motion/194) and [#204](https://khala.subsquare.io/council/motion/204) were not executed successfully due to the preimage / scheduler migration misconfiguration. This motion will try to re-execute Motion 194. Hopefully it can be executed correctly.

Please vote NAY to [#204](https://khala.subsquare.io/council/motion/204) because it sets a wrong preimage length. Vote on this proposal instead.

# Original Proposal

This motion will trigger two Transact message on Kusama to accept&send the HRMP request sent from InvArch Tinkernet.

The first transact will be performed on Kusama with the following call:

```
0x3c014d080000
```

which can be decoded as:

```
hrmp.hrmpAcceptOpenChannel(
  sender: 2,125,
)
```

The second transact will be performed on Kusama with the call:

```
0x3c004d080000e803000000900100
```

which can be decoded as:

```
hrmp.hrmpInitOpenChannel(
  recipient: 2,125,
  proposedMaxCapacity: 1,000
  proposedMaxMessageSize: 102,400
)
```


Khala's sovereign account has already got enough deposit to open the channels.

Accept & Open HRMP channel with InvArch Tinkernet (3) - motion #205

**Proposal purpose:**
The purpose of this proposal is to grow the Phala brand through continued developer relations. The requested funds will be specifically used to provide funding for builders in the Phala Network ecosystem who bring Phat Contract development forward through standardized development.
Which is crucial to enhancing Phala’s brand and invoking the support of developers that want to build on Phala Network.
This proposal shall allow the bounty proposers to act as child-bounty curators for submissions to the Phala’s builders program. Overall we aim to allow successful applicants and builders from the Phala Builders Program to become rewarded faster and on a regular basis.

**Context:**
With the upcoming launch of Phat Contracts and to support the growth of Phala’s killer product, the Phala team has launched the Phala Builders Program (PBP). This program provides funding, guidance, and support to developers that want to build high-value projects with Phat Contract, and add functionality to Phat Contract itself. 
The Phala Builders program was officially launched early February this year and is currently running within the application progress.
Since program launch, the BP team has received over 10 applications so far whereof already 2 applications have moved to the second phase of review.
The PBP offers funding to developers in up to 50k$ USD value in PHA token, paid out on-chain at agreed-upon intervals dictated by the Builder Agreement.

Besides the funding, teams will also receive technical assistance from lead Phat Contract developers during the design, testing, and deployment phases of project development.

Thirdly, marketing and network support can be requested. With this support, Phala can promote PBP projects through its own channels and within the Phala community.

**Expenditure:**
Overall, a treasury funding of 1 million dollars in PHA tokens is requested, which can support a maximum of up to 20 projects with the highest funding amount of 50kUSD. The bounty for this proposal is meant to be open-ended, with the funds being distributed through child-bounties aiming to reward builders' submissions and achievements of milestones in the Phala Builders Program.

All funds are being distributed directly to the applicants of the builders program. Applicants are eligible to receive funds, if they fall under following description:

<ins>Builders that want to build impossible Dapps</ins>
Within the builders program we want to support teams and individuals that are eager to push the limits of what smart contracts are capable of by incorporating an off-chain computation solution that utilizes a self-executing and tamper-proof model.
<ins>Teams and individuals that care about decentralization</ins>
We want to facilitate passionate builders that care about the need for decentralized web services and user-controlled digital infrastructure.
<ins>Developers that care about scalable trustless infrastructure </ins>
Teams and individuals which seek a computation solution that can handle any level of compute demand, and perform computation securely, privately, and trustlessly are necessary to expand the overall Phala Network ecosystem.

**Guidelines for Potential Applicants:**
The Phala Builders Program supports high-quality teams that have a solid understanding of the Phat Contract platform and a clear vision of how they will utilize Phat Contract within their project. Projects that come into the application process with a MVP or some level of existing development with Phat Contract are more likely to be successful in securing funding. 

**What we look for:**
<ins>Compelling Teams </ins>
Teams with strong technical backgrounds that have a clear vision for their project, including a growth strategy and structured plan of development. 
<ins>Innovative Ideas</ins>
As Phat Contract represents a new tool in the kit of Web3 developers, we’re looking to support projects that seek to push the envelope of what can be built on blockchain. We want to support new ideas that add something novel to the space. 
<ins>Contributions to Phat Contract tooling</ins>
As Phat Contract is a highly composable developer resource, we value teams that seek to build out new tooling and primitives within the SDK. 

**Application process for child-bounty implementers**
Applicants who receive funding through this bounty need to:
- follow the official application process described on the Phala wiki page: https://wiki.phala.network/en-us/build/general/builders-program/
- Submit their milestones for code review to Phala’s official github repo

**Funding Levels:**
<ins>Tier One </ins>
Maximum Value: $20,000 USD value paid in PHA
Criteria: Development of a compelling project involving significant usage of Phat Contract. 

<ins>Tier Two </ins>
Maximum Value: $50,000 USD value paid in PHA 
Criteria: Development of a compelling project or projects involving significant usage of Phat Contract, and the development of new tooling for Phat Contract. 

**Suggestions for this bounty:**
The proposal for the initial composition of the multisig, e.g. the curators, are four team members of Hashforest. The signatories of the general curator from Hashforest won’t receive any rewards.
We propose following Bounty Curators:
Marvin Tong, CEO of Hashforest and Co-founder of Phala Network
Hang Yin, CTO of Hashforest and Co-founder of Phala Network
Dr. Shelven Zhou, Lead Researcher and Partner at Hashforest and for Phala Network
Zoé Meckbach, VP of Growth at Phala Network and Partner at Hashforest
3 out of 4  yay votes are necessary for a child-bounty to get released.

The curators responsibilities:
General bounty curators will report back to council and create a report after every 3 months. This report will include the maximum PHA budget spent during the last three months. The post will be published in Phala’s forum.

Phala Builders Program funds - via Child Bounty distribution

Call hx: 0x2e5da25e0cf8685d9b16cb20dc2b58a92d558e5f963444bdb7dba316cefc73be
Date: 10/4-16/4, 2023
Requested allocation: 2050.17 USD =  14,230 PHA ( $0.1441, 7 days avg price in CMC) 

# Overview Of the Events
### Web 3 Festival - main event
[https://www.web3festival.org/hongkong2023/home?lang=en-US](url)

As one of the biggest Asia blockchain conferences,Web3 Festival is hosted by Wanxiang Blockchain Labs and HashKey Group each year in Shanghai until 2022. In 2023, it moved to HongKong for legal reasons. As the first large-scale (4 days) offline event held in China after Covid-19, this event has gathered a large number of blockchain practitioners and enthusiasts from home and abroad.

![](https://ibb.co/WymRMJK.png)
![](https://ibb.co/KmhdvWB.png)

We got a chance to share our brochures during the events. We’re invited by the host but we didn’t sponsor this event.

### Polkadot HongKong Workshop

PolkaWorld host a workshop for Polkadot during the HongKong crypto Week on April 11th. Ruby from Phala Network and the other 25 parachains participants join the event discussion. 100+ attendees attended this event to show their interest in Polkadot.

![](https://prnt.sc/pvH3fzWCEgSI.png)

### Asia crypto week side events

There were 160+ side events happen during the whole blockchain week. These events attracted blockchain experts, scholars, and entrepreneurs from all over the world, who shared the latest developments and achievements in blockchain technology. It showed us the passion for blockchain in Asia after opening up.

The week-long blockchain event included keynote speeches, roundtable discussions, project roadshows, and other sessions. During the event, participating guests will engage in in-depth exchanges on topics such as blockchain technology innovation, industry applications, investment and financing, and local policies and regulations in Hong Kong.

You can reviewed the whole list here or scan the QR code to learn more about

[https://img.foresightnews.pro/file/HK2023Event.png](url)

![](![image|646x330](upload://kIdvaQZU9sGy4Qx0u90mmNV4Abn.jpeg))

### Expense in HongKong

The costs here include airfare, hotel, and transportation for Phala team members. Details in the table below.

1 PHA = 0.1441 USD based on the 7-day average price on CMC.
|Expenses List||
|---|---|
|Item|USD|
|Flight|532.85|
|Hotel|1198.62|
|Brochure|87.21|
|Roll up|25.61|
|Transportation|203.7|
|VISA|2.18|
|Total|2050.17|






Phala at HongKong Blockchain Week - treasury proposal #70

Hello, Phala community 👋!
We are Slance, a fully remote Web3 animation studio.
Since 2020 we’ve helped 75+ growth-stage blockchain teams scale next level with animated pitch decks, promo videos and educational series. 
Our signature video style boosts brand credibility, visibility and helps build thriving communities.
Have a look at our show reel at [https://slance.co/ or https://youtube.com/slance/videos/](url). 

We are very much looking forward to working with the Phala community and are excited to produce the following videos for Phala:
- 1x educational video (1.5 minutes): $900
- 1x promo-explainer video (1.5 minutes): $900
- One-time fee of $250 (once per project, meant for asset library)
**Total cost: $2025**

**All video prices include**:
- One feedback round per production phase (1x script, 1x storyboard, 1x full length)
- Script, voice, music, design, animation
- English voice over (Male, US)
- No royalties, no watermarks, no copyright
- High-end quality, comparable to showreel productions
- 2-week production time

**Optional**: 
- Extra feedback round: +$95
- Export transitions / effects / elements into graphic files: $25
- Separate scenes into social shorts: +$25 / scene
- Subtitles (hardcoded): +$95 per language
- 4k production + export (future proof): +$250
- Purchase source file: 0.75% total cost 
- Thumbnail: +$35

**Project agreement**:
The project agreement that is signed and present in the Phala project folder applies to this proposal. 

**Note**
By submitting this proposal to the Phala treasury, no other legal binding documents or agreements go into effect, besides the project agreement above. Slance retains the full rights to creative freedom.

Videos service for Phat Contract intro series- treasury proposal #69

inDEX is a cross-chain dex aggregator designed to work on top of Phat Contract. This motion is a call to whitelist worker 0xf4dbaa37b64f78fa3f4a12132c257b6b3176beaa31fab6d6f15f9387de6fea44 on pallet-index. The worker is derived through Phat Contract, whose private key secured by Secure Enclave

worker

Whitelist inDEX worker for closed test - motion #200

# Please vote NAY to this motion and consider instead.

https://khala.subsquare.io/council/motion/205

----

# Original Proposal

[Motion #194](https://khala.subsquare.io/council/motion/194) was not executed successfully due to the preimage / scheduler migration problem. This motion will try to re-execute Motion 194. Hopefully it can be executed correctly.

# Original Proposal

This motion will trigger two Transact message on Kusama to accept&send the HRMP request sent from InvArch Tinkernet.

The first transact will be performed on Kusama with the following call:

```
0x3c014d080000
```

which can be decoded as:

```
hrmp.hrmpAcceptOpenChannel(
  sender: 2,125,
)
```

The second transact will be performed on Kusama with the call:

```
0x3c004d080000e803000000900100
```

which can be decoded as:

```
hrmp.hrmpInitOpenChannel(
  recipient: 2,125,
  proposedMaxCapacity: 1,000
  proposedMaxMessageSize: 102,400
)
```


Khala's sovereign account has already got enough deposit to open the channels.`

Accept & Open HRMP channel with InvArch Tinkernet (2) - motion #204

**Proposal #64 was submitted with the wrong PHA amount. This proposal #67 shall overwrite the old proposal #64.**

Phala has attended EthDenver 2023, the biggest Ethereum community event. The conference happened from February 27th to March 5th.
The Phala team on the ground attended following events:
EthDenver BUIDL week 2/27 - 3/2
Several events to meet partners, new users and potential Dapp builders
2 speaking engagements at Polkadot events
EthDenver main conference 3/2 - 3/5
2 day Phala booth

pictures of the whole conference tour can be found here: https://drive.google.com/drive/folders/1IvnY_6qxj25AgK7qua9FFdMSUU_F0RYV?usp=sharing

EthDenver BUIDL week 2/27 - 3/2

The Phala team had two speaking engagements at Polkadot events during the BUIDL week.
Phala’s CTO Hang Yin and friends from Manta Network and Crust Network got into a deep discussion about "Compute, Storage, and Privacy as a service that can be combined to build a fully functional cloud while keeping it decentralized.” The event and panel was hosted by the Parity team. It was an overall success to showcase Phala’s technological capabilities and discuss joint use cases with other parachain panelists.

Also Joshua Waller, Phala’s Developer Advocate was invited to speak at a Polkadot community event, organized by WebZero. Joshua delivered a powerful keynote on what’s next for Phat Contract at the Polkadot in USe event.

Our VP of Growth Zoé Meckbach and Global Head Ambassador of Polkadot moderated an insightful panel on the topic “Infrastructure and tooling for Web3” including an in-depth discussion on multi-party oracle aggregation for price feeds on Polkadot. The panel was joined by ecosystem teams SubQuery, Acurast and DIA.

EthDenver main conference March 2nd - March 5th:
The Phala team had a presence during the main conference with its own booth in the Polkadot Pavillion on March 2nd and March 4th. Overall many people came by the booth to learn about Phala Network and also have a look at the oracle demo.

Another highlight was that Rob Habermeier, co-founder of Polkadot, took some time to talk to the Phala team and learn about the upcoming Phat Contract release.

Key takeaways:
The Phala team met with a wide array of collaborators, partners, and ecosystem leaders at the conference, and made many new connections with industry-defining projects.

Off-Chain Compute is Picking Up Steam, which we have seen by announcements of several exciting off-chain infrastructure products. Including Chainlink Functions, and Gelato’s Web3 Functions.

The announcement of EIP-4337 had the conference buzzing about the amazing possibilities account abstraction opens up for UX improvements in crypto.
Phala can make Account Abstraction easier and more secure since the infrastructure to implement AA is heavily built off-chain. Phala offers verifiable off-chain compute

Zero Knowledge and Web3 UX were Hot Topics. Overall, ZKP became much more mature and a topic beyond privacy, e.g. people started to use ZKP to make off-chain compute verifiable. That said, ZKP and Secure Enclave tech are naturally complementary to each other.

Hang met with cybersecurity expert Andrew Miller to discuss best practices for TEE networks. Phala's unique design makes off-chain computation easy and verifiable
So we will explore how Phala can accelerate the evolution of Web3 industry

Expenses during the listed events
The reimbursement budget for all the listed events is the following:

Dates: February 27th - March 6th, 2023
Team members: 6 people: Hang Yin, Zhe Wang, Joshua Waller, Zoé Meckbach, Jojo Zhou, Stuart Brown
1 PHA = EMA30 of 3/27 by subscan.io 0.159 USD

item, Costs in USD (sum), PHA

Flights: 3,225 USD (6 ppl) = 20,283 PHA
Hotel: 6,003 USD (6 ppl) = 37,755 PHA
Swag: 1,909 USD (Reward) = 12,006
Others: 1,977 USD = 12,434
= Sum = 13,114 USD = 82,478 PHA

Treasury proposal for EthDenver

Dwellir is currently serving the Khala community with a public RPC endpoint service. We are serving on average **1,500,000** requests per day. A monthly increase with 239%.

This proposal is to cover the costs for January, February, March in 2023. 

Read the [full proposal here](https://docs.google.com/document/d/1JEhUxQn78QP3rsXwTribY_BBwWVbxsTtLbllVl0hyWU/edit?usp=sharing).

The PHA price has been calculated as the average prices over the last 30-days.

Dwellir - Public RPC Endpoint Service (Q2 2023)

This motion will mint 308.2M PHA and deposit it to SubBridge PHA reservation to enable PHA transfer. Once the motion is finished, the Phala team will bridge 308.2M PHA to the Phala compute reward pool.

[Gemini was launched on 8/4/2022](https://medium.com/phala-network/khala-gemini-upgrade-mining-reward-transaction-will-happen-around-2-00-a-m-utc-on-april-8th-97847474d7f0). Since then, Phala’s team had moved 381.8M PHA rewards from the locked compute reward subsidy reservation on Ethereum to the Khala subsidy pool in two separate transactions (Not including the 10M tokens transferred to Khala before Gemini started). 

There are still 127M tokens left in the Khala subsidy pool and 308.2M tokens locked in the Ethereum subsidy pool. 

This motion proposes that all the locked tokens in the Ethereum subsidy pool (308.2M PHA) are moved to the Phala subsidy pool to pay for the compute rewards to the workers on the Phala chain. 

In the future, we will periodically transfer funds between the Phala and Khala subsidy pools based on their balances to ensure that both chains have sufficient tokens to pay computation rewards. The rules for distributing rewards will be implemented by a dedicated budget balancer introduced in the referendum. More details can be found [here](https://khala.subsquare.io/democracy/referendum/89).

## Detailed Background

You can find both the Ethereum compute reward subsidy account and the Phala/Khala subsidy pool accounts here:

1. Ethereum (the biggest token holder on Etherscan) -[0x4731bc41b3cca4c2883b8ebb68cb546d5b3b4dd6](https://etherscan.io/token/0x6c5bA91642F10282b576d91922Ae6448C9d52f4E?a=0x4731bc41b3cca4c2883b8ebb68cb546d5b3b4dd6)
2. Phala — [modlphala/pp](https://phala.subscan.io/account/436H4jat7TobTbNYLdSJ3cmNy9K4frmE4Yuc4R2nNnaf56DL)
3. Khala — [modlphala/pp](https://khala.subscan.io/account/436H4jat7TobTbNYLdSJ3cmNy9K4frmE4Yuc4R2nNnaf56DL).

Since the genesis launch of Khala, 1% of the total PHA supply was moved from the Ethereum compute reward subsidy reservation to the Khala subsidy pool, according to Phala tokenomics. As 70% token is reserved for computing rewards, 69% was left in the Ethereum subsidy reservation.

After the Gemini Update, Khala and Phala will share the same compute reward schedule and subsidy pool. Therefore Phala team must move more funds to the Khala subsidy pool.

The first move after the Gemini Update happened on April 8th, 2022. The transaction amount is 226,800,000 PHA. And the second move happened on Feb 21st, 2023, with the amount of 155,000,000 PHA.

Adjust bridge reservation for the 308.2M PHA compute reward unlock - motion #197

This motion will trigger the runtime upgrade for Khala Network Runtime v1241. It is a bug fix for the WrappedBalances pallet.

For details, please check [here](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.24-khala-runtime-1241)

Khala Runtime Upgrade v1241 - motion #196

This motion will trigger two Transact message on Kusama to accept&send the HRMP request sent from InvArch Tinkernet.

The first transact will be performed on Kusama with the following call:

```
0x3c014d080000
```

which can be decoded as:

```
hrmp.hrmpAcceptOpenChannel(
  sender: 2,125,
)
```

The second transact will be performed on Kusama with the call:

```
0x3c004d080000e803000000900100
```

which can be decoded as:

```
hrmp.hrmpInitOpenChannel(
  recipient: 2,125,
  proposedMaxCapacity: 1,000
  proposedMaxMessageSize: 102,400
)
```


Khala's sovereign account has already got enough deposit to open the channels.

Accept & Open HRMP channel with InvArch Tinkernet - motion #194

This motion will trigger the runtime upgrade for Khala Network Runtime v1230. It is a new Khala runtime and client release with the following features:

- Add inDEX pallet
- Prepare for Phala Compute & Phat Contract launch
- Upgrade upstream substrate (Polkadot v0.9.40) with database stability improvements

For details, please check [here](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.23)

Khala Runtime Upgrade v1230 - motion #195

**Proponent/Paid to:** 41dYCD7Xx2Qhoph5CRQSTNeQWDJ7dpA1ZFNUvGK8RxUkrpkk

**Date:** 6th April 2023

**Total Requested PHA:** 31,232.9696 PHA 

**Short description:** Ongoing costs for Quarter 1 (January, February and March) of 2023, for the running of a high performance and reliable data indexing managed service for Phala Network.

**The full report can be found here:** [https://docs.google.com/document/d/1qRFm_U1td7BdfQyQhgvQnb0o2txEthC_GOg2CA7RBkc/edit?usp=sharing]([https://docs.google.com/document/d/1qRFm_U1td7BdfQyQhgvQnb0o2txEthC_GOg2CA7RBkc/edit?usp=sharing])

* * * * *

Original Motivation
================

Almost every blockchain has a need to process and query data, however everyone knows that a core weakness of blockchain data is that the processing and query performance is extremely inefficient. SubQuery is an open source platform that solves that.

Additionally, managing infrastructure can also be extremely challenging and many teams don't have the expertise or resource that is needed to deploy indexers to cloud providers and then run them at high availability so that they can be relied on for production use cases. SubQuery provides a hosted service with 99.9% reliability to remove this burden from teams,  so they can stay focused on building their dApps. 

Service Details 
================

Phala Network is currently leveraging SubQuery's enterprise-level managed service to provide reliable hosting for their SubQuery projects.  This critical service provides production data to applications built by the Phala Network team and the 99.9% uptime reliability ensures a seamless experience for the core team and their ecosystem.

Over the period of 2023-01-01 to 2023-03-31, SubQuery supported 5 different projects for Phala Network with a total of 9 (4 staging and 5 production) deployments. These projects were run in a shared database for a total of 19,439.9 compute hours. Each project deployment requires an indexing service, a compute service, and database access run in a production environment and monitored constantly to ensure availability.

Costings
--------

This proposal includes combined running costs for our infrastructure for Phala Network from 1st January 2023 until 31st March 2023. The total combined running cost is USD $4,859.975.

**Full report here:** [https://docs.google.com/document/d/1qRFm_U1td7BdfQyQhgvQnb0o2txEthC_GOg2CA7RBkc/edit?usp=sharing]([https://docs.google.com/document/d/1qRFm_U1td7BdfQyQhgvQnb0o2txEthC_GOg2CA7RBkc/edit?usp=sharing])

SubQuery Managed Service Solution (Q1, 2023)

**Proponent:** 42PDjUSugisVhhNQg453fkDwLmg9QMzeWe9huR817xt7c3DW

**Date:** 6th April 2023

**Total Requested PHA:**  98,389.9522 PHA

**Short description:** Ongoing costs for the running of high performance, scalable, and reliable public infrastructure for Phala.

**Full Proposal can be found here:** [https://docs.google.com/document/d/1K6FyI97QKWtdgQNpgWwFSs0YdH81uj8nPe6mFxxdUl4/edit#heading=h.xcq2u02l503a](https://docs.google.com/document/d/1K6FyI97QKWtdgQNpgWwFSs0YdH81uj8nPe6mFxxdUl4/edit#heading=h.xcq2u02l503a)

Original Motivation
===================

Setting up blockchain infrastructure is difficult, time consuming, and expensive:

-   It requires a level of server development expertise that many do not have

-   It's costly to run a full node nearly continuously, especially when your dApp's traffic is low and inconsistent. 

-   Running production level infrastructure is especially tricky. You need to autoscale quickly to handle bursty traffic, and you want to provide services in different regions around the world to provide low latency services - all of this is incredibly costly, but comes with significant economies of scale for a provider.

-   DevOps requires constant attention - time that would be better spent elsewhere building.

A shared node API service helps mitigate these barriers of entry to trying accessing a new protocol by reducing all these costs to near zero. We manage all the nodes for our users and distribute them across the world (with intelligent routing) to achieve global scalability from day 1, we monitor each node and ensure that they meet certain service levels, and we have the expertise and scale to handle production workloads and high peak traffic.

In summary, we try to reduce the pain of getting started on Khala and minimise the costs of accessing secure nodes while traffic from your dApp is low. When you grow, you can continue to use our shared API service, or we also [provide access to one click deploy dedicated Khala nodes](https://onfinality.io/dedicated_nodes) to any cloud of your choosing.

Service Details and Enhancements
================================

During Q1 of 2023, we've made a large number of stability improvements to our Ultimate API service to allow us to add a large number of new parachains over the last quarter as well as support for multiple chains outside of Polkadot.

For customers that do sign up for paid API keys, we've been adding more and more features to provide a better experience. Geolocation insights provide statistics about where in the world communities are to help influence decisions around where to expand infrastructure and to view the effectiveness of regional BD initiatives.  We can also now automatically upsize the storage on nodes to prevent the risk of any downtime.

Our customers are building cross-chain wallets, running some of the largest block explorers, and are indexing multiple networks - they've all benefited from these API access restrictions, improved monitoring, and the larger number of supported Polkadot chains.

Enhancements
------------

Additionally, we are proud to have delivered some key service enhancements that benefit the Polkadot ecosystem in the last quarter. This includes:

-   [Auto Expand Storage](https://blog.onfinality.io/onfinality-developer-update-auto-expand-storage-for-dedicated-nodes/) - When the node's storage reaches 85% utilisation, the storage size will be automatically increased by 10%. Saves developers and devOps time on having to constantly check on and manually upgrade their node storage size

-   [Partnership with POKT network](https://blog.onfinality.io/onfinality-partners-with-pocket-network-to-unlock-access-to-unstoppable-infrastructure/) to bring in more external developers into the Polkadot ecosystem

-   [Geographical Insights ](https://blog.onfinality.io/onfinality-adds-geolocation-insights-for-dapps-and-api-apps/)- API key owners can view statistics about where in the world your community are to help influence decisions around where to expand infrastructure and to view the effectiveness of regional BD initiatives

-   [Clarify our IP address handling](https://blog.onfinality.io/how-does-onfinality-deal-with-personal-information/) - OnFinality does not, and will never, correlate or link specific wallet addresses to the IP address or request origin making the RPC request

-   We're testing access to various unsafe methods like traceBlock and subscribeStorage that will help developers create applications that utilise XCM - contact us if you would like to be part of the beta

-   Reduced our exposure to any single cloud provider - Progressively migrated resources away from AWS to other cloud providers for lower cost and exposure.

-   Expanded our OnFinality for Startups Programme to support teams from the Substrate Builders Programme and Scytale Ventures

-   Added support for a number of new networks, including Ajuna, Unique, Clover, SORA, Composable Finance, Collectives, xx network, as well as Polygon, BNB, Fantom, Gnosis and Evmos from outside the ecosystem. OnFinality is a new one stop shop for all of your RPC needs from multiple ecosystems.

-   A variety of improvements to our health metric collection tools and automated recovery scripts to ensure our 99.9% SLA is exceeded.

-   Scale improvements to our team, processes, and systems to allow us to provide this same service to any  substrate team

You can always see live data on our API service on our public [status page](https://status.onfinality.io/) and [network analytics page](https://onfinality.io/networks).

**Full Proposal Here:** [https://docs.google.com/document/d/1K6FyI97QKWtdgQNpgWwFSs0YdH81uj8nPe6mFxxdUl4/edit#heading=h.xcq2u02l503a](https://docs.google.com/document/d/1K6FyI97QKWtdgQNpgWwFSs0YdH81uj8nPe6mFxxdUl4/edit#heading=h.xcq2u02l503a)

Proposal: High Performance Public Infrastructure (Q1 2023)

This motion will retry [motion #189](https://khala.subsquare.io/council/motion/189). The last motion was executed, but got overrode by motion #190 because Substrate only has one external proposal slot, and the newer one always overrides the earlier one.

## Original Proposal

This motion will [Proposal #20](https://khala.subsquare.io/democracy/proposal/20) to the external queue to accelerate the voting process. Once it's passed, the technical committee will fast track it (but still keep 7 days voting period).

Accelerate proposal #20: launch gemeni tokenomic on Phala (2nd try) - motion #191

This is a retry of the [motion #188](https://khala.subsquare.io/council/motion/188).

The original motion was not executed successfully because the permission was set incorrectly. It requires root permission to execute. So in this motion, we are going to execute the same steps but in a referenum.

## Original proposal

This motion is a batch call to fix the ChainBridge migration issue on ZLK after we upgrade to XCM v3.
With the new XCM version, `GeneralKey` definition was changed, which influence our resource id
and reserve account calculation on ChainBridge. The batch contains 6 calls:

1. Call-1 set ZLK to a temporary location `(1, X2(Parachain(2001), GeneralIndex(0))`
2. Call-2 set ZLK back to its real location `(1, X2(Parachain(2001), GeneralKey(2, 0x0207..00))`
The above two call will trigger ZLK resource id updated to proper value automatically
3. Call-3 force burn `196247848001219224432700` units ZLK from old reserve account(pub key): `0xde50ca45c8f7323ea372fd5d7929b9f37946690b0b668985beebe60431badcea`
4. Call-4 force mint `196247848001219224432700` units ZLK to new reserve account(pub key): `0x95f793efdd6b1f7894f6c4d9bcb3de87d4e58385c56ebf1bfef91f9ab2144b91`
5. Call-5 force burn `2026420000000000000000` units ZLK from temporary account: `427Xv1Y1bNNQ5XU6pCCVGbqTgEe41t6s4GAYCCCDwASWsXpa`
5. Call-6 force mint `2026420000000000000000` units LK to external account: `43L9xU7zKU2ByNKvsgb4QLnhBU4pVvfbphh52TeH8byRtPuj`

There are 5 transaction that have their ZLK locked in the temporary account: 
<https://khala.subscan.io/event?address=427Xv1Y1bNNQ5XU6pCCVGbqTgEe41t6s4GAYCCCDwASWsXpa&module=assets&event=issued&startDate=&endDate=&startBlock=&endBlock=&timeType=date&version=1220>

And the external account will bridge ZLK to user account on Moonriver



Council Motions