Halloy Hydra Community,

We are a team of builders and participants across various communities within the polkadot/substrate ecosystem.

We are brought together with a shared purpose, which is to turn nascent cross-chain infrastructure into a powerful and useful “playground of possibilities”.

**Mission**

The mission is to make it accessible and seamless to build cross chain workflows, across XCM(hrmp) and cross-chain infrastructure.

We want it to be useful for people of all levels (for technical, non-technical as well as generalists) within the ecosystem, (think of an open-source Zapier but for cross-chain Dapps).

![](https://lh6.googleusercontent.com/p9FE8G7vy1edhH8zt4YzmAG-kN-whbH2h6M6zV7WbwupJVlzdxoeCL3kJdxXqZsot_bcWWvVa3kFRq5ZlYI8Gbgt4LiP-OG228xLHoAz6dNbxJBnvIfZ8FEXHsxd5DhA3Zaj9HaQIb4I5KHgJyDtc1I)

Above is a very simple bagpipe to send DOT(Polkadot) to HydraDx.

**Create “Bagpipes”**

The nodal based canvass will allow users to weave together “Bagpipes”, which are complex workflows of actions that would typically take a  sweat and resources by technical people to put together.

Bagpipes can be as simple as sending or swapping assets, but it gets more interesting as you weave together more complex workflows. These workflows can then be for personal use, shared with other members of your team, or turned into cross-chain DApps.

**Examples to stimulate some ideas**

One near term example is **swapping DOT(on polkadot) for USDt (on asset hub)**, which sounds pretty boring and simple, but currently it requires sending your DOT to hydraDx from your wallet; then swapping on hydra; then sending to asset hub.

This currently takes multiple actions across probably more than one platform. With a bagpipe this can be done all in one signing ceremony and on one platform (once we integrate hydra swaps).

**3 actions on ~2 platforms into one action in one place**

**Minutes not weeks**

In the not-so-distant future, as we add more functionality (from different chains) into the canvass environment, anyone will be able to rapidly put together workflow possibilities that many of us have yet to consider.

As the variety of features (that you can drag and drop onto the canvas) compounds, so do the possibilities increase (exponentially).

It can take minutes rather than days or weeks to put novel and useful workflows that will contain a variety of features from various chains, including: assets, DEX, GOV, NFT, Identity, Scheduling, staking, trading etc.

The project is open source under the MIT license and you can access XCMSend by:

-   1: Build it yourself(docs: [https://xcmsend.github.io/deployments/debian.html](https://xcmsend.github.io/deployments/debian.html))
-   2: Use the public instance at: [https://app.xcmsend.com/](https://app.xcmsend.com/)
-   3: use the public docker image([https://hub.docker.com/r/xcmsend/xcmsend](https://hub.docker.com/r/xcmsend/xcmsend))

We would love for you to try it out, to get a sense of the vision and possibility and to provide some constructive feedback we can use, and which will inform what features we build and prioritize.

**What we’ve done**

We’ve integrated the basic functionality so that you can send hydraDx to polkadot and other parachains.

**Enabling Swaps**

![](https://lh4.googleusercontent.com/_52d17D_dxR3U08c6wk3cinDu50qnlIqV2znCciqO03OzrYar9Cv_wiNI-PFIUDt9VBvN7TuFuDv6in8552enxDYrKA4MUC3sO9MfL9ax1VMUp3LPiQFUU_TOfhL09y8UG97iI1qbyd8OTc5YHodUwM)

Polkadot (DOT) ->xTransfer-> HydraDx (DOT) ->Swap-> HydraDx(USDt) -> xTransfer -> AssetHub.

**Near Term priority**

The next order of tasks we want to prioritize is swapping functionality.

**Weaving together influential communities (Near Term) Roadmap**

-   HydraDx
-   Interlay
-   Wormhole
**…**

**What we’d love to do**

After gaining community feedback on our new project, we wish to seek treasury funding for enabling swaps using the HydraDx SDK, Omnipool, and spot price orders.

This swapping feature will enable anyone to interact with the Omnipool dex and build them into their “Bagpipe” workflows.

**Useful links:**

[https://xcmsend.github.io/chapter\_1.html](https://xcmsend.github.io/chapter_1.html)

[https://hub.docker.com/r/xcmsend/xcmsend](https://hub.docker.com/r/xcmsend/xcmsend)

[https://github.com/XcmSend/app-v0.0.1](https://github.com/XcmSend/app-v0.0.1)

[https://decentration.medium.com/a-workflow-builder-adds-a-playground-on-top-of-cross-chain-infrastructure-25222617ed8](https://decentration.medium.com/a-workflow-builder-adds-a-playground-on-top-of-cross-chain-infrastructure-25222617ed8)

Note: The UX is still in beta, so do only keep amounts small until we release our stable version.

Thanks and please share some feedback in the comments!:)


SubSquare is a team of builders and participants who want to make it easy for people to build cross-chain workflows. They have created a nodal based canvas to weave together "Bagpipes", which are complex workflows of actions that can be used for personal use, shared with others, or turned into cross-chain DApps. They have integrated basic functionality so that you can send hydraDx to Polkadot and other parachains. Their next priority is swapping functionality. They want to seek treasury funding for enabling swaps using the HydraDx SDK, Omnipool, and spot price orders. The project is open source under the MIT license and you can access XCMSend by building it yourself, using the public instance, or using the public docker image.

[Feedback wanted] XCMSend

Hey Hydrators,
For the past two months, I have been a community manager in two Telegram chats related to HydraDX and Basilisk in the Russian-speaking community as well as highly engaged in creating HydraDX related content and publishing it on Twitter and Telegram. 
**Period of contribution:** 2023/01/09-2023/01/11 (2 months)

**Breakdown of my duties and contributions as a HydraDX community manager:**
• HydraDX Polkadot DCA Treasury content and graphics. 
• Creating the pipeline for video creation, planning to start publishing series of videos next month.
• Answering frequently asked questions 
• Translating all official announcements and passing on important information to community members 
• Encouraging the community to participate in governance 
• Announcing all recent updates and alpha that I find on HydraDX twitter or EN community 
• Dealing with FUD and false allegations related to HydraDX & Basilisk 
• Twitter engagement related to HydraDX social media and updates 
• Creating HydraDX educational content and promoting it on Twitter and Telegram. 
• Currently translating the HydraDX documentation and polishing it for the merge.
https://johnm-1.gitbook.io/hydradx-tekhnicheskaya-dokumentaciya/

**Requested tips:** Average hours per week for community moderation and content creation: 15 hours  
**Total hours for 2 month:** 8 weeks * 15 = 120 hours 
**The last 7 days average price:** 0,007219 (120 * 20/0,007219) = 332,456 HDX (Basic salary of community managers + content creation + translation)  
**Total HDX requested: 320,000 HDX**
Cheers Hydrators!

HydraDX is a platform that has a community manager who helps people understand and use it. 

The community manager does many things like making videos, answering questions, and translating important information. 

They also create educational content and promote it on social media. 

The community manager works for 15 hours a week and has worked for 2 months. 

They are requesting to be paid 320,000 HDX for their work.

[Tip request] JOHNM Community Manager + Content creation September-October

<h1>Period of the contribution:</h1>11/09/2023-31/10/2023<h1>Summary:</h1>Create and manage the HydraDX/Basilisk Chinese community (<a href="https://t.me/HydraDX_China" rel="noopener noreferrer" target="_blank">Telegram</a>/Discord/WeChat/QQ). Translation and Video Production. Write and publish articles on China's self-media platforms.<h1>Requested tips:</h1>475845 HDX in total, of which:<ol><li data-list="bullet">352174 HDX (72.9*20/0.00414) - Basic salary of community managers</li><li data-list="bullet">123671 HDX (25.6*20/0.00414) - Translation and Video Production</li><li data-list="bullet">0 HDX (0.0000001*20/0.00414) - Articles published and forwarded</li></ol>*$0.00414 - 7D average price from Grafana（1-11-2023）*<h1>Description: </h1><h2>Basic salary of community managers</h2>Create the HydraDX/Basilisk Chinese Community in the Telegram/WeChat. Recently, I created a QQ group (Group No: 308908086). At present, daily communication and text AMA are mainly carried out in the WeChat group - 蛇粉总群. Translate official help announcements in time and publish them in the community. Answer questions from community members in time. Organize and host a monthly/quarterly text AMA. Organize a team of community volunteers to complete translation tasks in time.Salary time interval: Sept. 11 – Oct. 31, a total of 51 days, equivalent to 7.29 weeks. 10 hours per week for a total of 72.9 hours.<h2>Translation and Video Production</h2>In the past two months, I translated 8 official help documents and 2 blog post, which took 12.6 hours:<ol><li data-list="ordered"> <a href="https://docs.hydradx.io/cn/staking" rel="noopener noreferrer" target="_blank">Staking </a> (Time taken: 1.5h)</li><li data-list="ordered"> <a href="https://docs.hydradx.io/cn/howto_stake" rel="noopener noreferrer" target="_blank">Stake HDX</a> (Time taken: 0.5h)</li><li data-list="ordered">HDX Tokenomics (Re-translation after the content of the English document has been changed. Time taken: 0.2h)</li><li data-list="ordered">State of the Art Security (Re-translation after the content of the English document has been changed. Time taken: 0.8h)</li><li data-list="ordered">The Great Unlock (Time taken: 0.8h)</li><li data-list="ordered">Bonds (Time taken: 1h)</li><li data-list="ordered">Liquidity bootstrapping (LBP) (Time taken: 1.5h)</li><li data-list="ordered">Acquire Bonds (LBP) (Time taken: 0.8h)</li></ol>Note: The md document of Chinese document No. 3-8 has been uploaded to github, but it has not been merged yet. <img src="https://s3.bmp.ovh/imgs/2023/10/26/2a13daf3f5e9c977.png"><ol><li data-list="ordered"> <a href="https://mp.weixin.qq.com/s/YGnNTGfc8zb-l3VqAAQpaw" rel="noopener noreferrer" target="_blank">8 Months of HydraDX Omnipool</a> (Time taken: 2.5h)</li><li data-list="ordered"> <a href="https://mp.weixin.qq.com/s/v-BWVsoUVnf9oPB_3kYUFQ" rel="noopener noreferrer" target="_blank">HydraDX Monthly - September 2023</a> (Time taken: 3h)</li></ol>In the past two months, I made 7 videos, which took 13 hours (This is just the application time, the actual time x2+). The list is as follows:<ol><li data-list="ordered"><a href="https://www.bilibili.com/video/BV1xK4y1c7Ri/?share_source=copy_web&amp;vd_source=15657f65b763e75f26127fc19147f849" rel="noopener noreferrer" target="_blank">HDX Staking 2.0 Is Coming</a> (Time taken: 1h)</li><li data-list="ordered"><a href="https://www.bilibili.com/video/BV1Bk4y1F7y8/?share_source=copy_web&amp;vd_source=15657f65b763e75f26127fc19147f849" rel="noopener noreferrer" target="_blank">5 Tips For Crypto Players</a> (Time taken: 2h)</li><li data-list="ordered"><a href="https://www.bilibili.com/video/BV1gF411S7La/?share_source=copy_web&amp;vd_source=15657f65b763e75f26127fc19147f849" rel="noopener noreferrer" target="_blank">Let’s Get Closer To HydraDX</a> (Time taken: 1h)</li><li data-list="ordered"><a href="https://www.bilibili.com/video/BV1jK4y1w7LP/?share_source=copy_web&amp;vd_source=15657f65b763e75f26127fc19147f849" rel="noopener noreferrer" target="_blank">A Quick Look At The Main Features Of HydraDX</a> (Time taken: 3h)</li><li data-list="ordered"><a href="https://www.bilibili.com/video/BV1em4y1G7ZS/?share_source=copy_web&amp;vd_source=15657f65b763e75f26127fc19147f849" rel="noopener noreferrer" target="_blank">The Capital Behind HydraDX - Investor Introduction</a> (Time taken: 2h)</li><li data-list="ordered"><a href="https://www.bilibili.com/video/BV1d34y1A74h/?share_source=copy_web&amp;vd_source=15657f65b763e75f26127fc19147f849" rel="noopener noreferrer" target="_blank">HydraDX Project Timeline - The Road To Innovation</a> (Time taken: 3h)</li><li data-list="ordered"><a href="https://www.bilibili.com/video/BV1494y1a7Am/?share_source=copy_web&amp;vd_source=15657f65b763e75f26127fc19147f849" rel="noopener noreferrer" target="_blank">Why Should I Hold HDX</a> (Time taken: 1h)&nbsp;</li></ol><h2>Articles published and forwarded</h2>Currently, if you enter "HydraDX" on <a href="https://www.baidu.com/s?wd=HydraDX&amp;rsv_spt=1&amp;rsv_iqid=0xf095392d0007268c&amp;issp=1&amp;f=3&amp;rsv_bp=1&amp;rsv_idx=2&amp;ie=utf-8&amp;tn=40020637_7_oem_dg&amp;rsv_enter=1&amp;rsv_dl=ih_0&amp;rsv_sug3=1&amp;rsv_sug1=1&amp;rsv_sug7=001&amp;rsv_sug2=1&amp;rsv_btype=i&amp;rsp=0&amp;rsv_sug9=es_2_1&amp;rsv_sug4=2147&amp;rsv_sug=9" rel="noopener noreferrer" target="_blank">Baidu </a>- the most popular search engine in China, almost all of the top-ranked articles were published by me.In the past two months, 1 article was published and forwarded 4 times, which took 0.0000001 hours:<ol><li data-list="bullet"><a href="https://zhuanlan.zhihu.com/p/658094013" rel="noopener noreferrer" target="_blank">Link1</a></li><li data-list="bullet"><a href="https://page.om.qq.com/page/OSp50o2dvvuldt5BngnpIB5Q0" rel="noopener noreferrer" target="_blank">Link2</a></li><li data-list="bullet"><a href="https://baijiahao.baidu.com/builder/preview/s?id=1777892611945298070" rel="noopener noreferrer" target="_blank">Link3</a></li><li data-list="bullet"><a href="https://weibo.com/ttarticle/p/show?id=2309404949479584563633" rel="noopener noreferrer" target="_blank">Link4</a></li></ol> Stay hydrated!

- A person wants to create and manage a Chinese community for HydraDX/Basilisk on various platforms like Telegram, Discord, WeChat, and QQ.
- They will translate official announcements and write articles about HydraDX/Basilisk for Chinese media platforms.
- They will also organize monthly/quarterly text AMA sessions and manage a team of volunteers for translation tasks.
- They will work for 10 hours per week for a total of 72.9 hours and will be paid a basic salary of 352174 HDX and 123671 HDX for translation and video production.
- They have already published articles and videos about HydraDX/Basilisk and are well-known in the Chinese community.

[Tip Request] Chinese Community Manager

28 June - 15 November : 895,522  HDX- Comunnity Manneging

Use the Last 7 Days avg price from Grafana : 0.0067
Avg hours per week in that time: 15h

Details: In the moderation of the community, I was present answering the doubts, HydraDX groups, telegram and discord.

Thanks to the team for letting me be part of this great project, we hope we continue to grow and progress.

Adress: 7NzNFJb2pfy2mZzdS2ky8okkXZL52fn2VAvAsc8jigvCtBec

Tip treasury - Jose Crypto- (June-November)

- Requested Tip USD: $ 6480, 9 x 720$.
- Requested Tip: 1,296,000 HDX ($0.005/HDX).
- Beneficiary: 7KTvkdHvwFTWretzgAUwpvfSvYJGEFPe1zefbiguFRfxBVvk
- Timespan: 9 Months (Q2, Q3 and Q4 of 2023).

---
SubSquare is a governance platform for substrate based blockchains, and we have been continually maintaining the deployments for HydraDX. We propose a treasury tip to support the work.

## Work scope

- Daily devops/monitor work to keep the deployment well running.
- Track and update common dependencies like polkadot api.
- Receive feedbacks and bug fixes.
- Part of delivered enhancement features
    - Governance data statistics.
    - Notifications by telegram.
    - Calendar feature with which we can see history/future events with a calendar view.
    - User votes management and any user's voting history.


## Part of development plans
- Off chain data decentralization.
- Delegation UI enhancement.
- On-chain governance deposit management.

SubSquare is a platform for blockchain governance.
They want to get paid for maintaining the deployments for HydraDX.
They are asking for a tip of $6480 or 1,296,000 HDX.
This work will take 9 months.
Their work includes daily monitoring, bug fixes, and adding new features.
They also plan to improve the user interface and add new governance features.

[Tip Request]Subsquare maintenance request from 2023.04 to 2023.12

Hello Hydrators!

As most of you will be aware, **our first parachain slot will come to an end at the beginning of January**.

We agreed as a community as part of [referendum #43](https://hydradx.subsquare.io/democracy/referenda/43) that we could diversify up to 1M DAI into DOT in preparation for bidding on a second parachain slot (approximately 216,000 DOT at current prices) - the fortunate news is that currently slots are generally going for <70,000 DOT (with the exception of Crowdloans which typically overpay); so whilst [DCAs for DOT are ongoing](https://hydradx.subsquare.io/democracy/referenda/86), we should have sufficient DOT already in the Treasury to cover this requirement.

Intergalactic Council along the with HydraDX Council have looked at and discussed a range of methods for executing these auctions bids in the most permissionless yet dynamic way possible - with the intention to reduce counterparty risk but also not overpay for the slot. The best method to achieve these goals is as follows:

- Create a **pure proxy on Polkadot** which we will transfer (through governance) e.g. 100,000 DOT from HydraDX Treasury
- Assign parachain 2034 (HydraDX) as `ANY PROXY`
- Assign a 2/6 multisig of the following HydraDX council members as `AUCTION PROXY`:
 - Jak-Pan
 - mrq
 - lolmcshizz
 - Leemo
 - Jose Crypto
 - Dakauaiguy
- The multisig would then be able to **bid on upcoming auctions** from those DOT, **without having any capability to move the funds**

I have created the following schema to demonstrate the setup.
![image.png](https://subsquare.infura-ipfs.io/ipfs/QmWcZwPDgHQehTnoHbHcfG4aRmckd9SvVAFGuGoKSbGHHG)

Before taking the next steps on-chain, I wanted to have a discussion to answer any questions that may arise around this process. The intention will then be to have everything ready to begin bidding for a slot from auction #55 onwards (once Parallel have overpaid for #54).

HydraDX is preparing to bid on a second parachain slot on Polkadot.

They agreed to diversify up to 1M DAI into DOT in preparation for bidding on a second parachain slot.

Currently, slots are generally going for less than 70,000 DOT.

They plan to create a pure proxy on Polkadot and assign a 2/6 multisig of the HydraDX council members to bid on upcoming auctions.

The multisig would be able to bid on upcoming auctions from those DOT without having any capability to move the funds.

Parachain slot renewal

On 10/06, I was a speaker at a cryptocurrency event in Curitiba, Brazil, aimed at crypto enthusiasts. The event focused on various blockchain networks, and I was representing Polkadot as an ambassador. I seized the opportunity to have 16 HydraDx T-shirts made for distribution among some of the participants. It was a relatively small event with about 50 attendees, but it brought together people from various blockchain networks with diverse interests. I believe it was a highly productive event, as around 10 individuals who attended later joined the HydraDxBrasil Telegram group. The Brazilian community around HydraDx is continuously growing.

At the last minute, I managed to secure a slot with the event organizers to also talk about HydraDx Brasil. I adapted a presentation that @lolmcshizz shared with me (from Polkadot Decoded) and spoke to the audience about omniPool, DCA, splitting, and upcoming developments in HydraDx. It was a great event.

The request for tips here is to cover the costs of the T-shirts that I gave away at the event.

16 T-shirts
Each T-shirt cost $7,60 USD.

16 * 7.60 = $121,60 USD
Delivery fee: $10 USD
Total: $131,60 USD

131.60 x 0,00441568 = 29802,88 HDX
Total: 29802,88 HDX

PS: Below are photos of some people who won the T-shirts.

I did not request tips for the time I spent preparing and scripting the presentation because it was a last-minute situation, and I didn't have the opportunity to inform the council members beforehand. However, if you feel that there is no problem, please let me know, and I can create a new tip request. I dedicated approximately 5 hours to fine-tune the presentation, create a script, and deliver the speech.


![](https://i.postimg.cc/MHbkgHL6/IMG-20231009-WA00321.jpg)

![](https://i.postimg.cc/wMd8WL04/IMG-20231009-WA00351.jpg)
![](https://i.postimg.cc/7Ldy2p7k/IMG-20231009-WA00371.jpg)
![](https://i.postimg.cc/hGfBhSXs/IMG-20231009-WA00381.jpg)
![](https://i.postimg.cc/XY2WVZYX/IMG-20231009-WA00391.jpg)
![](https://i.postimg.cc/vBnwL3L6/IMG-20231009-WA00401.jpg)
![](https://i.postimg.cc/Vks1Q913/IMG-20231010-WA0006.jpg)
![](https://i.postimg.cc/h49qXZtk/IMG-20231006-162834-685.jpg)

- A person spoke at a cryptocurrency event in Brazil about a blockchain network called Polkadot.
- They gave away 16 T-shirts with a different blockchain network called HydraDx on them.
- The event had about 50 people, and some of them joined the HydraDxBrasil Telegram group later.
- The person also talked about HydraDx Brasil and its developments during the event.
- They are requesting tips to cover the cost of the T-shirts, which is $131.60 USD or 29802.88 HDX.

tips for t-shirts - Event in Curitiba City

gm Hydratooooors,

We are currently in the process of withdrawing our Wormhole (Acala) assets and swapping them for Wormhole (Moonbeam) [MRL] assets as per [this discussion](https://hydradx.subsquare.io/posts/102).

We are also **imminently going to be launching our Stablepools feature** (finally!), meaning that when our DAI > USDC OTC order is filled, we will be launching USDC (native) directly into a Stablepool with USDT (native). We currently have between 2-2.1M DAI allocated as Omnipool liquidity.

In order to reduce our "bridge risk", we should not include DAI in a Stablepool with our native assets - that being said, we *do* need to have means of low slippage swaps between bridged and native stablecoins. **I believe we can leverage MRL, Stablepools & Omnipool to provide a low-slippage decentralised stablecoins onboarding route into our ecosystem.**

----

My proposal is as follows:

- **Diversify some of the ~2M DAI** allocated as Omnipool liquidity (currently split between Acala & Moonbeam wormhole assets) into:
    - 300K DAI (MRL)
    - 300K USDC (MRL)
    - 300K USDT (MRL)
    - 300K USDC (or T) (native)
- Place those assets into a **4pool** Stablepool
- Deposit the 4pool asset shares into the Omnipool

This will compliment our other **2pool** Stablepool - USDC/ USDT (native) - which will also have its' asset shares deposited into the Omnipool. (liquidity will likely be ~2.6M worth of each, 2.2M current allocation + 800K of the existing DAI allocation)

The combination of these two Stablepools, deposited into the Omnipool will:
- Allow HydraDX to operate as an onboarding route for DAI/USDT/USDC liquidity from Ethereum to Polkadot native stablecoins, with minimal price impact
- Maintain stablecoin liquidity in the Omnipool at the current agreed ~6.6M across DAI/USDT/USDC
- Reduce reliance on bridged versions of stablecoins and limit the impact of any risk on our protocol owned native stablecoins
- Improve efficiency of swaps involving stablecoins

----

I have raised this discussion now, as we are currently in the process of swapping DAI (Acala Wormhole) for MRL versions - however, it would make sense to OTC the DAI directly into USDT (MRL)/ USDC (MRL)/USDC (native) instead of swapping to DAI (MRL) and then swapping once more for each of those assets.

Happy to answer any questions - **stay hydrated**!

----

**EDIT:** I have updated the numbers to ~300K of each of the assets in the MRL 4pool, as the research work we've done on the A parameters suggests that this will provide ample liquidity for the onboarding of liquidity. The remaining DAI from this allocation will be redirected towards native stablecoins.

HydraDX is withdrawing assets and swapping them for new ones. They are launching a Stablepools feature and allocating 2-2.1M DAI as Omnipool liquidity. They want to reduce their "bridge risk" and provide a low-slippage decentralized stablecoins onboarding route. They propose diversifying 2M DAI allocated as Omnipool liquidity into a 4pool Stablepool and depositing the asset shares into the Omnipool. This will allow HydraDX to operate as an onboarding route for DAI/USDT/USDC liquidity from Ethereum to Polkadot native stablecoins, with minimal price impact. They will maintain stablecoin liquidity in the Omnipool and reduce reliance on bridged versions of stablecoins.

Diversification of MRL DAI

Dear HydraDX Community,

I'd like to share my thoughts on optimizing our approach to subsidized staking rewards, integrating ideas that can attract genuine users while minimizing opportunistic behavior during high-yield staking periods. Additionally, I'll reference relevant psychological studies related to marketing to support this proposal.

Proposal: A Gradual Subsidy Release Strategy

I propose adopting a strategy that involves several phases to ensure sustained user engagement and manage expectations effectively:

Initial Staking Period: Begin with a phase of staking without subsidies. This allows users to experience the platform without immediate financial incentives, promoting genuine interest and commitment.

Slow Subsidy Release: Followed by a gradual release of subsidies from the treasury leading up to a predetermined fixed date. This gradual increase in rewards aligns with users' psychological responses to incremental incentives, fostering a sense of gradual growth.

Max Subsidy Period: Introduce a period of maximum subsidies from the treasury, as initially planned. This phase capitalizes on high-yield incentives while balancing the need for user sustainability.

Tapering Off: Subsequently, initiate a controlled tapering of subsidies to encourage long-term engagement even after the high-yield phase ends.

Psychological Considerations and Marketing Insights

Psychological studies in marketing highlight the importance of aligning user expectations with actual outcomes. Emission-based incentives can sometimes create unrealistic hopes, leading to disappointment among users and investors when reality sets in. To mitigate this, a phased approach that gradually builds rewards addresses these expectations, creating a more genuine and sustainable user base.

Additionally, the proposed strategy acknowledges the unique dynamics of web3 users. Unlike traditional web2 environments, web3 users are often incentivized to be positive due to financial considerations. Hence, it's crucial to set expectations that reflect real-world scenarios while still encouraging genuine participation.

Incorporating the ideas of a leading then trailing subsidy to and from a fixed date is a powerful way to strike a balance. It helps users set realistic expectations and also rewards early adopters for their commitment, aligning with both web3 user behaviors and established marketing principles.

Ultimately, my aim is to foster a robust community of users who are genuinely interested in HydraDX for its potential and utility, rather than solely for short-term financial gains.

I look forward to engaging with the community on this topic and welcome your thoughts and feedback.

Cheers.

Lucacrypto

1. The writer proposes a new strategy for staking rewards on the HydraDX platform.
2. The new strategy involves several phases, including an initial period without subsidies, a gradual increase in rewards, a high-yield period, and a controlled tapering off.
3. The writer cites psychological studies in marketing to support the proposed strategy, emphasizing the importance of aligning user expectations with actual outcomes.
4. The proposed strategy aims to foster a more genuine and sustainable user base on the platform.
5. The writer invites feedback and engagement from the HydraDX community on the proposed strategy.

staking rewards

<h1>Period of the contribution:</h1>2023/08/11-2023/09/10<h3>Summary:</h3>Create the HydraDX/Basilisk Chinese community. Participate in the translation/proofreading. Published articles on China's self-media platforms.<h1>Requested tips:</h1>140984HDX&nbsp;in total, of which:<ol><li data-list="ordered">132042HDX (44.3*20/0.00671) - Basic salary of community managers</li><li data-list="ordered">8942HDX (3*20/0.00671) - Translation and Video Production</li><li data-list="ordered">0HDX (0.0000001*20/0.00671) - Articles published</li></ol>0.00671 - 7D average price from Grafana（2023-09-11）<h1>Description:</h1><h2>Basic salary of community managers</h2>Create the HydraDX/Basilisk Chinese Community in the Telegram and WeChat(At present, daily communication and text AMA are mainly carried out in the WeChat group - 蛇粉总群). Translate official announcements in time and publish them in the community. Answer questions from community members in time. Organize and host a monthly text AMA. Organize a team of community volunteers to complete translation/proofreading tasks in a timely manner.Salary time interval: Aug 11 - Sep 10, a total of 31 days, equivalent to 4.43 weeks. 10 hours per week for a total of&nbsp;44.3 hours.<h2>Translation</h2>This month, I translated 1 article and it took&nbsp;3 hours：<ol><li data-list="ordered"><a href="https://mp.weixin.qq.com/s/_n5zgJEKuqWMQp--S1qCPQ" rel="noopener noreferrer" target="_blank">The Return of HDX Staking</a></li></ol><h2>Articles published</h2><a href="https://mp.weixin.qq.com/s/_n5zgJEKuqWMQp--S1qCPQ" rel="noopener noreferrer" target="_blank">1 article</a> was published and forwarded 4 times, which took 0.0000001 hours:<ol><li data-list="ordered"><a href="https://page.om.qq.com/page/OHH6pEO328BPEp6_puavxpFw0" rel="noopener noreferrer" target="_blank">link</a></li><li data-list="ordered"><a href="https://mbd.baidu.com/newspage/data/landingshare?preview=1&amp;pageType=1&amp;isBdboxFrom=1&amp;context=%7B%22nid%22%3A%22news_9764382953746236289%22%2C%22sourceFrom%22%3A%22bjh%22%7D" rel="noopener noreferrer" target="_blank">link</a></li><li data-list="ordered"><a href="https://zhuanlan.zhihu.com/p/655452598" rel="noopener noreferrer" target="_blank">link</a></li><li data-list="ordered"><a href="https://weibo.com/ttarticle/p/show?id=2309404944570638270766" rel="noopener noreferrer" target="_blank">link</a></li></ol> Stay hydrated!

- A person helped create a community for HydraDX/Basilisk in China.
- They translated official announcements and answered community members' questions.
- They organized a monthly text AMA and a team of volunteers for translation/proofreading.
- They were paid a basic salary of 132042HDX for 44.3 hours of work and 8942HDX for translation and video production.
- They also published one article and it took 3 hours to translate.

11.08.2023 I send in Nova wallet 2 transaction (look at foto).
https://i.postimg.cc/k59YQCHS/photo-2023-08-07-09-55-15.jpg
Transaction 2 - i use https://app.hydradx.io/cross-chain (cross-chain HydraDX - ASTR in app)
Transaction 1 - i send in Nowa wallet (erroneous transaction from the application "Nowa wallet" interface). I sent it to HydraDX parachain account directly...
Transaction https://astar.subscan.io/extrinsic/0x093a214e0288f48e1007568c2c938e2d9ca30c493429eb5f9b0ff8e1186b9a62
My ASTR adress XwvFqwGxd7vUFde3DsYbyTb69dbU5AJVDvprRdd257P5qbt
My HydraDX adress
7KcBFPLfFVr5Xf6Ya6tvWEtEaHveehgVRn4SY4w5sfbfQTRo
I also provide screenshots of correspondence with members of Team HydraDX and Nova Wallet with their confirmation of the authenticity of my words.
I sincerely ask you to return my funds back. This is too high a price to pay for my stupidity...
Foto
https://i.postimg.cc/xT2fbJRT/photo-2023-09-12-21-21-24-2.jpg
https://i.postimg.cc/66dww6Xs/photo-2023-09-12-21-21-24.jpg


- On August 8th, 2023, the author made two transactions using the Nova wallet.
- The second transaction involved using the cross-chain HydraDX-ASTR feature on the app.
- The first transaction was sent in error directly to the HydraDX parachain account.
- The author provides their ASTR and HydraDX addresses and a link to the transaction on Subscan.
- The author has provided screenshots of correspondence with members of Team HydraDX and Nova Wallet to confirm the authenticity of their claim and requests the return of their funds.

Send back the funds that were mistakenly sent to the parchain wallet to the stupid user who did it...

Period of the contribution: 6,7,8/2023

Summary:
https://hydradxczsk.substack.com/p/hydradx-mesacny-update-c-4
https://hydradxczsk.substack.com/p/hydradx-mesacny-update-c-5
https://hydradxczsk.substack.com/p/hydradx-mesacny-update-jul-2023

Time spent: 6 hrs

Requested tip: 18 598 HDX (20USD / 7D Avg 0,006452 x 6)

Description: Translation 3 newsletters to Slovak language for CZ/SK Hydra community and its distribution on social platforms (different groups and channels Facebook, Twitter, Discord) (4,5 hrs) + community work (chats, activity on social media platforms...) 1,5 hrs 

- Someone spent 6 hours translating newsletters about HydraDX for a community in Slovakia and the Czech Republic.
- They translated 3 newsletters and shared them on social media platforms like Facebook, Twitter, and Discord.
- They also spent time chatting with the community and being active on social media for 1.5 hours.
- They are requesting a tip of 18,598 HDX, which is worth about $20 USD.
- This contribution was made in June, July, and August of 2023.

[Tip request] Slovak translations for CZ/SK community

Hey Hydratooooors,

For the past two months, I have been a community manager in two Telegram chats related to HydraDX and Basilisk in the Russian-speaking community as well as highly engaged in creating HydraDX related content and publishing it on Twitter and Telegram.
**Period of contribution:** 2023/01/07-2023/01/09 (2 months)

**Breakdown of my duties and contributions as a HydraDX community manager:**
	•	HydraDX DCA content and graphics. Working on a tutorial video atm. 
	•	Answering frequently asked questions
	•	Translating all official announcements and passing on important information to community members
	•	Encouraging the community to participate in governance
	•	Announcing all recent updates and alpha that I find on HydraDX twitter or EN community
	•	Dealing with FUD and false allegations related to HydraDX & Basilisk
	•	Twitter engagement related to HydraDX social media and updates
	•	Creating HydraDX educational content and promoting it on Twitter and Telegram.
	•	Hosted an AMA session with RU community in our TG chat

**Requested tips:** 
Average hours per week for community moderation and content creation: 15 hours 
Total hours for 2 month: 8 weeks * 15 = 120 hours
The last 7 days' average price: 0,006677
(120 * 20/0,006677) = 359,442 HDX (Basic salary of community managers + content creation) 
**Total HDX requested:** **320,000 HDX**

Cheers Hydratooooors!

HydraDX is a project that has a community manager who helps people understand and use it.
The community manager creates videos, answers questions, and shares important information with the community.
They also encourage people to participate in making decisions about HydraDX.
The community manager deals with any false information about HydraDX and promotes educational content.
They work about 15 hours per week and are requesting 320,000 HDX for their 2 months of work.

[Tip request] JOHNM Community Manager + Content creation July-August

**UPDATE ON 31st AUGUST** 


After working on five months and investing countless number of hours. We didn't get anything. I just lived with the false hope from this community. One message from the council member and everything is vanished. Sometimes life hit you hard with a brick.

We will not be translating any content from next month. Thanks for all the opportunity. [@Jose Crypto](7NzNFJb2pfy2mZzdS2ky8okkXZL52fn2VAvAsc8jigvCtBec-hydradx) [@lolmcshizz](7Ljigfve9PdRqvSjiRGUjVf37rbX3n89ZmaitD2hQQhtLBMN-hydradx) [@YUNG BEEF 4.2](7MYesC9hELWbdCefydppjcNuA5rxaBJdecuFBGHEaNpJ876i-hydradx) 



- A group of people worked hard for five months but didn't achieve anything.
- They feel disappointed and let down by the community.
- They will not be translating any content from next month.
- They thanked some people named Jose Crypto, lolmcshizz, and YUNG BEEF 4.2.
- The post ends with a sad note.

Update on Persian and Urdu Translation Articles 

Period of Contribution - 03/2023- 05/2023

Summary of all the articles:

I have been running two blogs for Persian and Urdu community.

https://hydradxpersian.wordpress.com/

https://hydradxurdu.wordpress.com/

(https://docs.google.com/document/d/1D0L2HVZ-RSGVvkvgPKvEd-wByMGsvnvpPxwup8tnwXw/edit?usp=sharing)

Time Spent : 125.19 hrs

Requested Tip : 352,390 HDX ( 20USD / 7D Avg 0,007103 x 125.19)

Description : For translating the 20 articles in Persian and 5 articles in Urdu.

Previously I have translated the book Polkadot for Beginners (https://linktr.ee/polkadotbook)

I will be thankful to all the council members  if they can support me in this initiative.



- The person has two blogs, one for Persian and one for Urdu community.
- They have spent over 125 hours translating articles for these blogs.
- They have translated 20 articles in Persian and 5 articles in Urdu.
- They have previously translated a book called Polkadot for Beginners.
- They are requesting a tip of 352,390 HDX (which is equivalent to 20 USD) for their translation work.

Tip Request for Urdu and Persian Articles 

The proposal titled "Don't get Rekt" emphasizes the critical need for governance participation in HydraDX, especially in light of the upcoming integration of 700K BNC tokens from Bifrost. Highlighting a potential risk from unmonitored proposals, it recommends a strategic investment of $10,000 in Bifrost tokens over 14 days, delegation to Chaos DAO, and a stipend of $2,000 to Chaos DAO for their monitoring and bot development. These actions aim to protect liquidity and underscore the importance of vigilant oversight to prevent significant financial loss within the ecosystem.

https://docs.google.com/document/d/16_cBMZva2ahPtqeo1BtBZz71agw1VHe_VSqZ_3RZ2zk/edit?usp=sharing



- The proposal is about a platform called HydraDX and the need for people to participate in its governance.
- There is a risk of losing money if proposals are not monitored carefully.
- The proposal suggests investing $10,000 in Bifrost tokens over 14 days and delegating to Chaos DAO.
- Chaos DAO will receive a stipend of $2,000 for monitoring and bot development.
- These actions will help protect the platform's liquidity and prevent financial loss.

Don't get Rekt - Protecting HydraDX interests across the polkadot ecosystem

Dearest Hydratooooors,

With the imminent launch of staking on HydraDX - I would like to propose that we subsidise staking rewards for the first year... my rationale is as follows:

- Stakers receive rewards every period (1 day) from a `reward pot` - in the initial design (Staking v1.0) this `pot` is filled solely by HDX trading fees. In later implementations (Staking v2.0) this will also receive trading fees from POL LP.
- Initially, due to low volumes, I expect that these trading fees will be low.
- Through DCA from POL DAI, the Treasury is currently accumulating HDX.
- A portion of these HDX could be distributed to HDX stakers in order to reward early supporters, whilst the protocol continues to be developed and HydraDX builds traction.

My proposal would be to take `22,222,222` HDX from the HydraDX Treasury, and distribute it evenly throughout `365 periods` to the `reward pot`.

I have been playing around with numbers on [this sheet](https://docs.google.com/spreadsheets/d/1KoQKL3m--6rr_pYxGU66zlqgb-hV4T83QsyeqINUXsE/edit?usp=sharing) - if we assume that 10% of circulating supply stake their HDX, then the subsidised HDX rewards would provide a ~8.6% APR (non-inflationary).

Looking forward to this discussion!

HydraDX is launching staking soon and the proposal is to subsidize staking rewards for the first year. 
Stakers receive rewards every day from a reward pot which is filled by HDX trading fees. 
Initially, these trading fees are expected to be low due to low volumes. 
HydraDX Treasury is accumulating HDX through DCA from POL DAI. 
22,222,222 HDX could be distributed evenly over 365 periods to the reward pot to reward early supporters.

Subsidise HDX staking for 1 year

Greetings Hydra-heads,

Now that we have HRMP channels open with Moonbeam, I believe that now could be a great opportunity to explore additional liquidity routes for the Omnipool - namely, in this discussion, I would like to propose that we remove:

- **Liquidity position #1165** - 175.9611 shares of **WETH** - currently worth ~ 175.66 WETH + ~ 687.71 LRNA (~$344K)
- **Liquidity position #1166** - 280,343 shares of **DAI** - currently worth ~ 301,119 DAI
- **Liquidity position #1769** - 11.2523 shares of **WBTC** - currently worth ~ 10.133 WBTC + ~ 925.79 LRNA (~$324K)

After removal, we should seek to replace these withdrawn Acala (Wormhole) assets with the Moonbeam (Wormhole) equivalents, before adding them to the Omnipool. This will open up liquidity flows from the Moonbeam ecosystem - which currently has significantly higher ERC-20 volumes than the Acala ecosystem, and allows for increasingly efficient arbs and additional onboarding routes for our users.

Many community members have mentioned in the past that they wish to see us explore Moonbeam as a liquidity onboarding route, so here I am proposing a plan for discussion before any action is taken.

Thanks!

Here's a summary of the post in 5 bullet points:

- The writer wants to explore additional liquidity routes for the Omnipool.
- They propose to remove three liquidity positions from Acala (Wormhole) and replace them with Moonbeam (Wormhole) equivalents.
- This will open up liquidity flows from the Moonbeam ecosystem, which has higher ERC-20 volumes than the Acala ecosystem.
- The proposed plan is up for discussion before any action is taken.
- This could be a good opportunity to onboard more users and make things more efficient.

Remove part of DAI, WBTC & WETH POL from Omnipool for Moonbeam Wormhole

<h1>Period of the contribution:</h1>2023/07/01-2023/08/10<h3>Summary:</h3>Create the HydraDX/Basilisk Chinese community. Participate in the translation/proofreading. Published articles on China's self-media platforms.<h1>Requested tips:</h1>200872HDX in total, of which:<ol><li data-list="ordered">170349HDX (58.6*20/0.00688) - Basic salary of community managers</li><li data-list="ordered">30523HDX (10.5*20/0.00688) - Translation and Video Production</li><li data-list="ordered">0HDX (0.0000001*20/0.00688) - Articles published</li></ol>0.00688 - 7D average price from Grafana<h1>Description:</h1><h2>Basic salary of community managers</h2>Create the HydraDX/Basilisk Chinese Community in the Telegram and WeChat(At present, daily communication and text AMA are mainly carried out in the WeChat group - 蛇粉总群). Translate official announcements in time and publish them in the community. Answer questions from community members in time. Organize and host a monthly text AMA. Organize a team of community volunteers to complete translation/proofreading tasks in a timely manner.Salary time interval: July 1-August 10, a total of 41 days, equivalent to 5.86weeks. 10 hours per week for a total of 58.6 hours.<h2>Translation and Video Production</h2>This month, I translated 6 articles and it took 8 hours：<ol><li data-list="ordered"><a href="https://mp.weixin.qq.com/s/zoXLvtIQlTbQ45XuuTeuBA" rel="noopener noreferrer" target="_blank">HydraDX Monthly Update #5</a>（2hrs）</li><li data-list="ordered"><a href="https://mp.weixin.qq.com/s/GcqweDgro1k4cEykcu0aVw" rel="noopener noreferrer" target="_blank">HydraDX Monthly Update - July 2023</a>（2hrs）</li><li data-list="ordered"><a href="https://docs.hydradx.io/cn/howto_hydrated_farms/" rel="noopener noreferrer" target="_blank">Join Hydrated Farms</a>（1hr）</li><li data-list="ordered">DCA Trading（1hr）</li><li data-list="ordered">Place a DCA Order（1hr）</li><li data-list="ordered">Hydrated Farms（1hr）</li></ol>The last three articles have been translated and the md document has been uploaded, waiting to be merged!<img src="https://s3.bmp.ovh/imgs/2023/08/11/c2fefac4551a617e.png"><a href="https://mp.weixin.qq.com/s/MLkMuDHJbCOlnHdYvQgaLA" rel="noopener noreferrer" target="_blank">Provide Chinese voice and subtitles for the first official promotional video - "HydraDX Omnipool - Intro"</a>, which took a total of 2.5 hours. Among them, the translation took 1 hour, the Chinese voice fine production took 1 hour, and the subtitle adjustment took 0.5 hours.<h2>Articles published</h2>2 articles were published, which took 0.0000001hrs:<ol><li data-list="ordered"><a href="https://mp.weixin.qq.com/s/zoXLvtIQlTbQ45XuuTeuBA" rel="noopener noreferrer" target="_blank">Link1</a></li><li data-list="ordered"><a href="https://mp.weixin.qq.com/s/GcqweDgro1k4cEykcu0aVw" rel="noopener noreferrer" target="_blank">Link2</a></li></ol> Stay hydrated!

- A person helped create a community for HydraDX/Basilisk in China.
- They translated official announcements and answered questions from community members.
- They organized and hosted a monthly text AMA.
- They translated 6 articles and created Chinese voice and subtitles for a promotional video.
- They also published 2 articles.

[Tips Request] Chinese Community Manager - July

**Proponent:** 7KMzGDKDNKjUrdiiZd6q8UzxfnPrDQmpjgS3CyLwQBWCtbgd

**Date:** 18th July 2023

**Amount Requested:** 308,662.4630 HDX

**Short description:** OnFinality has been running high performance, scalable, and reliable public infrastructure for HydraDX since December 2022, in this proposal we only request reimbursement for the costs incurred in Q2 (April, May, June) of 2023.

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

* * * * *

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 HydraDX 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 HydraDX nodes](https://onfinality.io/dedicated_nodes)  to any cloud of your choosing. 

Background on our RPC Service
=============================

Since inception in November 2020 we have made a large number of improvements to our Ultimate API service focussing on three key areas; performance/reliability, providing more value from our Ultimate API service, and cost optimisation.

### Performance/Reliability

OnFinality is operationally striving for a minimum of 99.99% reliability, which means less than an hour of downtime each year.  We proudly display and share our [90 day uptime statistics](https://status.onfinality.io/) for each network publicly [here](https://status.onfinality.io/uptime/r40wwpclbwzm).

We have invested hugely into a team dedicated to optimising our application gateway and caching layer to ensure that we provide the fastest possible service for our customers. We run clusters in 5 different regions (North Virginia, Frankfurt, Tokyo, Singapore, and Australia) and across 3 different cloud providers (AWS, GCP, Alicloud) to ensure that we are fault tolerant to any single region or cloud provider ceasing service.

### Providing more value from our Ultimate API service

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](https://blog.onfinality.io/onfinality-adds-geolocation-insights-for-dapps-and-api-apps/) 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](https://blog.onfinality.io/onfinality-developer-update-auto-expand-storage-for-dedicated-nodes/) to prevent the risk of any downtime.

Finally, in Q2 of 2023 OnFinality [launched Trace API](https://blog.onfinality.io/onfinality-launches-trace-api-for-unprecedented-visibility-into-your-dapps/) support which was a huge enhancement allowing unprecedented visibility for dApp builders. Trace API captures and records vital information otherwise not available through regular RPC methods and extrinsics (such as complete XCM transfer records and complete list of balance changes). These APIs are essential in order for [developers like Polkaholic](https://blog.onfinality.io/onfinalitys-new-trace-api-helping-colorful-notion-get-trace-data-from-over-40-substrate-chains/) to parse and understand XCM transactions.

### Cost Optimisation

OnFinality is very conscious about providing a strong level of support for HydraDX  at an extremely competitive price. Cost saving measurement has been a significant focus on behalf of our customers, with advanced rate limiting controls implemented. We can, for example, rate limit each client on a burst and sustained basis and based on the request methods that they are calling (e.g. each state_traceBlock request is rate limited 45x more than chain_getBlock), [read more about these advanced rate limiting tools that we've developed here](https://documentation.onfinality.io/support/public-rate-limits).

Meaning that we can continue to provide generous public API endpoints for over 40 different networks for common-good applications, but restrict access to high volume users that abuse this free service. We've been able to manage our costs significantly on behalf of our customers as a result. 

We've [developed and shared our approach towards service sustainability](https://polkadot.polkassembly.io/post/1270), with the introduction of a 'Paid API Revenue Share Discount' scheme. In this scheme OnFinality pools the revenue from customers that pay for higher API pricing plans and distributes this revenue pool to partners that currently pay for and own each API endpoint proportionally based on the number of paid API requests that go to that API endpoint. 

Our cost optimisation efforts were validated in Q1 as we had the lowest cost per million responses across all of the major RPC providers that lodged a proposal to the Polkadot treasury. You can see how our costs compared to other RPC providers in the ecosystem during Q1 [here](https://docs.google.com/spreadsheets/d/1Utw2HfS7I5Gpyhrl9ejuj0CrQ4AcChGFteXdw0a8tro/edit#gid=0).

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

During Q2 of 2023, we've made a number of new improvements to our Ultimate API service that address performance/reliability, features, and costs.

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

-   [Launched Trace API](https://blog.onfinality.io/onfinality-launches-trace-api-for-unprecedented-visibility-into-your-dapps/) allowing unprecedented visibility for dApp builders. Trace API captures and records vital information otherwise not available through regular RPC methods and extrinsics (such as complete XCM transfer records and complete list of balance changes). These APIs are essential in order for [developers like Polkaholic](https://blog.onfinality.io/onfinalitys-new-trace-api-helping-colorful-notion-get-trace-data-from-over-40-substrate-chains/) to parse and understand XCM transactions.

-   [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

-   Added support for a number of new networks, including Anmol, HydraDX, Equilibrium, as well as Osmosis, Evmos, Harmony, Arbitrum, Optimism, Fuse, DFK Chain, Celo, and Klaytn 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

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. You can always see live data on our API service on our public [status page](https://status.onfinality.io/).

Costings
--------

OnFinality has been running our high performance infrastructure for the HydraDX community since December 2022 however this proposal only requests reimbursement for combined running costs of our infrastructure for HydraDX in Q2 (April, May, June) 2023.

The total combined running cost is a fixed price of  $620 per month (total USD $1,860). This fixed price is all inclusive for our managed service including monitoring, alerting, support, maintenance such as version upgrades, and our intelligent gateway.

|HydraDX Total (USD)|$1,860.00|
|:----|:----|
|HDX Conversion Rate|US$0.006026|
|Total HDX Due|HDX 308,662.4630|

The HDX conversion rate was retrieved from CoinMarketCap using the 30 day time weighted average price ending on 2023-06-30.

**For more details, read the full report here:** [https://docs.google.com/document/d/1zxV6K3x0EfkN0ZNnTlJZ0W2geXj0zr_ercDUY465RXs/edit?usp=sharing](https://docs.google.com/document/d/1zxV6K3x0EfkN0ZNnTlJZ0W2geXj0zr_ercDUY465RXs/edit?usp=sharing)

OnFinality is a company that helps people set up blockchain infrastructure for their dApps. They manage all the nodes for their users and distribute them across the world to achieve global scalability from day 1. They have made a large number of improvements to their Ultimate API service, focusing on performance/reliability, providing more value from their Ultimate API service, and cost optimization. They have launched Trace API, allowing unprecedented visibility for dApp builders. They have added support for a number of new networks, including Anmol, HydraDX, Equilibrium, as well as Osmosis, Evmos, Harmony, Arbitrum, Optimism, Fuse, DFK Chain, Celo, and Klaytn from outside the ecosystem. They have been running their high-performance infrastructure for the HydraDX community since December 2022, and this proposal only requests reimbursement for combined running costs of their infrastructure for HydraDX in Q2 (April, May, June) 2023.

OnFinality High Performance Public Infrastructure (Q2, 2023)

Period of the contribution: 04+05/2023

Summary:
https://hydradxczsk.substack.com/p/hydradx-mesacny-update-c-2
https://hydradxczsk.substack.com/p/hydradx-mesacny-update-c-3
SK Hydra docs 

Time spent: 50 hrs

Requested tip: 140 785 HDX (20USD / 7D Avg 0,007103 x 50)

Description: Translation 2 newsletters to Slovak language for CZ/SK Hydra community and its distribution in Fb groups (4 hrs) + community work (chats, activity on social media platforms...) 4 hrs + Update and addition of Hydra docs SK version 42 hrs

- Someone spent 50 hours working on a project related to CZ/SK Hydra community.
- They translated 2 newsletters to Slovak language and distributed them in Facebook groups.
- They also did community work such as chatting and being active on social media platforms for 4 hours.
- They spent 42 hours updating and adding Hydra docs in Slovak language.
- They are requesting a tip of 140,785 HDX (which is equivalent to 20 USD) for their work.

<h2>Period of the contribution:</h2>2023/06/01-2023/06/30Summary:Create the HydraDX/Basilisk Chinese community. Participate in the translation/proofreading. Published articles on China's self-media platforms.<h2>Requested tips:</h2>128060HDX&nbsp;in total, of which:<ol><li data-list="ordered">128060HDX (42.9*20/0.0067)&nbsp;- Basic salary of community managers</li><li data-list="ordered">0HDX (0.00001*20/0.0067)&nbsp;-&nbsp;Participate in the translation/proofreading</li><li data-list="ordered">0HDX (0.00001*20/0.0067)&nbsp;- Published articles on China's self-media platforms</li></ol><h2>Description:</h2><h3>Basic salary of community managers</h3>Create&nbsp;<a href="https://t.me/HydraDX_China" rel="noopener noreferrer" target="_blank">the HydraDX/Basilisk Chinese Community</a>&nbsp;in the Telegram and WeChat(At present, daily communication and text AMA are mainly carried out in the WeChat group - 蛇粉总群). Translate official announcements in time and publish them in the community. Answer questions from community members in time. Organize and host a monthly text AMA. Organize a team of community volunteers to complete translation/proofreading tasks in a timely manner (Unfortunately, the main translator has left the translation team due to dissatisfaction with the reward payment amount. Starting from June, I will complete the translation task independently).Salary time interval: June 1-30, a total of 30 days, equivalent to 4.29 weeks. 10 hours per week for a total of&nbsp;42.9&nbsp;hours.<h3>Participated in translation and proofreading</h3>This month, I translated&nbsp;1&nbsp;article and it took&nbsp;0.00001&nbsp;hours.The translated article is:HydraDX Monthly Update #4<h3>Published articles on China's self-media platforms</h3>1 article was published, which took 0.00001hr:<a href="https://mp.weixin.qq.com/s/aAIprrA1ftgcxe7vSqB9TQ" rel="noopener noreferrer" target="_blank">https://mp.weixin.qq.com/s/aAIprrA1ftgcxe7vSqB9TQ</a>&nbsp;Stay hydrated!

1. A person is creating a Chinese community for HydraDX/Basilisk.
2. They will communicate with the community through WeChat and Telegram.
3. They will translate official announcements and answer community questions.
4. They will organize monthly text AMA and complete translation/proofreading tasks.
5. They will receive a basic salary and have published one article on China's self-media platform.

[Tips Request] Chinese Community Manager – June

 5 April- 28 June: 1074620 HDX- Comunnity Manneging

Use the Last 7 Days avg price from Grafana : 0.0067
Avg hours per week in that time: 30h

Details: In the moderation of the community, I was present answering the doubts, HydraDX groups, telegram and discord.

Thanks to the team for letting me be part of this great project, we hope we continue to grow and progress.

Adress: 7NzNFJb2pfy2mZzdS2ky8okkXZL52fn2VAvAsc8jigvCtBec

Tip treasury - Jose Crypto- (April-June)

Period of the contribution: 2023/5/01-2023/5/31

Summary: English to Chinese translation

Requested tip:23098.6HDX (8.2*20/0.0071=23098.6， 7d Ma price on 2023-6-01 ,from Kraken : 0.0071)

Time spent: 8.2hr

Description:
The translated articles are as follows:
1. [Hydradx-monthly-update-2](https://mp.weixin.qq.com/s/UAbZFvVxUIruBu3okU5xMQ)
![](https://s3.bmp.ovh/imgs/2023/06/01/af9d53037748f31f.png)
Stay hydrated! 
Bullish on HydraDX ！
Keep building ！


[Tips Request] English to Chinese translation

# Proposed DCA schedule for Treasury Q2+ diversification strategy
In [Referendum #43](https://hydradx.subsquare.io/democracy/referendum/43) the HydraDX community approved the diversification of a combined 4.8M DAI into HDX, DOT and iBTC using the DCA pallet once deployed.

As we approach the launch of this key feature, it is important that we discuss the schedule for execution. This will not be a formal “vote”, as each individual DCA schedule will require its own referenda to be executed through the Treasury - instead this discussion will gauge alignment and identify any conflicts or concerns.

### Buy 1,000,000 DAI worth of HDX
- Execute a DAI > HDX trade every 5 blocks (~60 seconds)
- Aim to execute the entirety of the order over 1 quarter (13 weeks)
- This would result in ~131,000 sells of 7.63 DAI in exchange for HDX
- In order to gauge performance and adjust if needed, I propose an initial schedule of 50,000 DAI, followed by 3x 250,000 DAI, and finally 200,000 DAI until the budget is depleted
### Buy 3,330,000 DAI worth of DOT
- Execute a DAI > DOT trade every 2 blocks (~24 seconds)
- Aim to execute the entirety of the order over 1 quarter (13 weeks)
- This would result in ~328,000 sells of 10.16 DAI in exchange for DOT
- In order to gauge performance and adjust if needed, I propose an initial schedule of 50,000 DAI, followed by 6x 500,000 DAI, and finally 280,000 DAI until the budget is depleted
### Buy 500,000 DAI worth of iBTC
- Execute a DAI > iBTC trade every 5 blocks
- Aim to execute the entirety of the order over 6 weeks
- This would result in ~60,000 sells of 8.27 DAI in exchange for iBTC
- In order to gauge performance and adjust if needed, I propose an initial schedule of 50,000 DAI, followed by 3x 150,000 DAI until the budget is depleted

-----
Please leave your comments in this discussion, as well as indicating your preference on the poll.


- HydraDX community approved diversification of 4.8M DAI into HDX, DOT, and iBTC using DCA pallet.
- A proposed schedule for execution of DCA strategy is being discussed.
- The proposal suggests buying 1,000,000 DAI worth of HDX, 3,330,000 DAI worth of DOT, and 500,000 DAI worth of iBTC.
- The proposal includes executing trades every few seconds or minutes over a period of 6-13 weeks.
- The proposal includes an initial schedule to gauge performance and make adjustments if needed.

Discussions