You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As described in DeFiCh/dfips#187, we operate an independent, loadbalanced OCEAN in several data centers at different providers, distributed in Europe.
Our solution primarily serves as a fallback in case the official Ocean Infrastructure at AWS is not available.
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.
Since we don't want to get ahead of ourselves with the costs, we are requesting the Q1/2023 costs in this round as well, since it looks like there will not be another Voting Round this year in terms of timing.
The entire amount will be spent on infrastructure costs for Q1 2023 (~$2000 per month with a DFI-price of 0.63$).
How does this CFP benefit the DeFiChain community?
In the last 4 months we could see from the statistics that our infrastructure is used and was ready as a fallback, when at the beginning of September the official infrastructure had a problem and was not available. The accesses have increased x4 in this time and has shown us that the fallback works so that we want to continue to operate our Ocean.
Another example of this was a few days ago, when the official OCEAN URL was classified as malicious by various DNS servers due to a false positive and as a result the LightWallet could no longer be used with the official URL. (https://twitter.com/uzyn/status/1585804113593659392)
Our infrastructure was available as a fallback and we noticed a doubling of requests to mydefichain Ocean in the statistics.
The text was updated successfully, but these errors were encountered:
Stonygan
changed the title
CFP: mydefichain Ocean Q1/2023 (4,000 DFI)
CFP: mydefichain Ocean Q1/2023 (9,500 DFI)
Oct 24, 2022
Overview
Requester(s): mydefichain
Amount requested in DFI: 9,500
Receiving address: dFRtR9GJT9UF41UgjHNusxeZpKqy8nRun3
Reddit discussion thread: https://www.reddit.com/r/defiblockchain/comments/ykgqqg/cfp_mydefichain_ocean_q42022_9500_dfi_and_q12023/
Proposal fee (95 DFI) txid: aec158a3070554d479c72873427a71e44ba2a4f8bd89853aea27c5e712878078
Describe the purpose
As described in DeFiCh/dfips#187, we operate an independent, loadbalanced OCEAN in several data centers at different providers, distributed in Europe.
Our solution primarily serves as a fallback in case the official Ocean Infrastructure at AWS is not available.
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.
We also operate our own OCEAN infrastructure for the testnet: https://testnet-ocean.mydefichain.com:8443
How will the fund be spent?
Since we don't want to get ahead of ourselves with the costs, we are requesting the Q1/2023 costs in this round as well, since it looks like there will not be another Voting Round this year in terms of timing.
The entire amount will be spent on infrastructure costs for Q1 2023 (~$2000 per month with a DFI-price of 0.63$).
How does this CFP benefit the DeFiChain community?
In the last 4 months we could see from the statistics that our infrastructure is used and was ready as a fallback, when at the beginning of September the official infrastructure had a problem and was not available. The accesses have increased x4 in this time and has shown us that the fallback works so that we want to continue to operate our Ocean.
Another example of this was a few days ago, when the official OCEAN URL was classified as malicious by various DNS servers due to a false positive and as a result the LightWallet could no longer be used with the official URL. (https://twitter.com/uzyn/status/1585804113593659392)
Our infrastructure was available as a fallback and we noticed a doubling of requests to mydefichain Ocean in the statistics.
The text was updated successfully, but these errors were encountered: