mydefichain-Ocean-2023-cycle-3

[virgchiniwala]

Overview

Requester(s): u/Stonygan Amount requested in DFI: 11,000 Cycles: 3/6 Receiving address: dFRtR9GJT9UF41UgjHNusxeZpKqy8nRun3 Reddit discussion thread (optional): https://www.reddit.com/r/defiblockchain/comments/12qhhj5/mydefichain_ocean_2023_actual_cycle_round/

Describe the purpose

Planned cycle votings for 2023: Cycle 1 ends on Block 2860000, estimated 2023-04-20 (approved, 6850 DFI, 0,55$/DFI)

Cycle 2 ends on Block 2990000, estimated 2023-06-04 (approved, 7500 DFI, 0,50$/DFI)

Cycle 3 ends on Block 3120000, estimated 2023-07-19 (Actual Cycle Round, 11000 DFI, 0,35$/DFI)

Cycle 4 ends on Block 3250000, estimated 2023-09-02 (Next Cycle, 11.000 DFI, 0,34$/DFI)

Cycle 5 ends on Block 3380000, estimated 2023-10-17 (upcoming)

Cycle 6 ends on Block 3510000, estimated 2023-12-01 (upcoming)

Hello Community,

to take decentralization further, we are providing an independent Ocean API that can be used by anyone in the Light Wallet or by other community projects.The infrastructure is intended to be a fallback for the official Ocean API and can be used by DeFiChain users in case of failure.

At the moment we operate Servers in different Providers and Datacenters in Europe: Paris (France), Vienna (Austria), Frankfurt, Berlin, Duesseldorf and Nuernberg (Germany)The servers can be accessed via a unique URL (https://ocean.mydefichain.com/), behind that a load balancer takes over the distribution of the requests. (https://testnet-ocean.mydefichain.com:8443/ for Testnet)The Load Balancer operate as a Master and Backup Load Balancer in active/passive mode with a Highly Available IP address (a special highly available address, which is routed to the master Load Balancer instance) Should the master instances experience a failure, this address is automatically rerouted to the backup one.Master and backup are running on different hardware clusters to ensure that they don't share physical resources and minimize the risk of a simultaneous failure.

We believe that an independent provider from the official Ocean infrastructure is not only important for decentralization, but should and can serve as a fallback especially in case of failure of the official endpoint. Our statistics have shown over the last weeks that our infrastructure is often used as an alternative in case of problems.

Requests

Filesystem Growth last 400 days.

How much in the Lightwallet used our Ocean, even if there was no error in the Ocean infrastructure, our statistics show at the beginning of January, when the Lightwallet contained an error and the setting for custom endpoints was buggy and did not work (https://github.com/WavesHQ/walletkit/pull/73), our number of hits dropped significantly as a result and only increased again when this problem was fixed with a new version for iOS and Android at the beginning of february.

Problem with custom Service provider

How will the fund be spent?

To always see the current status of our Ocean infrastructure, we have created a fork of defiscan.live, which has our own Ocean infrastructure for the Mainnet and Testnet permanently stored as a custom service provider.

So if defiscan.live fails due to problems, our explorer can be used as an alternative:

https://explorer.mydefichain.com/

Due to the increased requirements, primarily in disk storage, and the increased prices of all providers since the beginning of the year, the monthly cost is 2500$ for the cloud infrastructure, which we herewith request from the Masternodes for 2023 in 6 cycles. The entire amount of each cycle ( ~6 weeks) will be spent on infrastructure costs ( ~$2500 per month).