profile
viewpoint
Chris Remus chris-remus @Chainflow chainflow.io Founder @Chainflow and Staking Defense / Proof of Stake network advisor / Crypto Project & Product Manager / Aspiring Bodhisattva & Cyclist

chris-remus/althea-zone 0

Configuration and documentation for the Althea cosmos zone

chris-remus/aragon-wiki 0

The Aragon wiki

chris-remus/betanet 0

Configuration files for the Betanet

chris-remus/celo-monorepo 0

Official repository for core projects comprising the Celo platform

chris-remus/core 0

Golang implementation of the Terra Protocol

chris-remus/cosmos-sdk 0

:chains: Blockchain Application Framework :sparkles:

push eventChainflow/celo

Chris Remus

commit sha af4bb0d2532d58f23b0728e6e736b4e37d614263

Update celo-key-backup-on-change.sh

view details

push time in 5 days

push eventChainflow/celo

Chris Remus

commit sha 5787f8c7b89217b3acdee3acb97d26fc379f2152

Create celo-key-backup-on-change.service

view details

push time in 5 days

push eventChainflow/celo

Chris Remus

commit sha 77e74452e6a14e88d9abe3f8c12f1018c5671ae6

Create celo-key-backup-on-change.sh

view details

push time in 5 days

push eventChainflow/celo

Chris Remus

commit sha ca953a33171bc749331d30dd97e9fb2af07611d6

Rename node-monitoring-bot to celo-node-monitoring-bot

view details

push time in 10 days

push eventChainflow/celo

Chris Remus

commit sha 5b0f2769a634ca8b70cd8c8d83d4f8f2ba358b3c

Create node-monitoring-bot

view details

push time in 10 days

create barnchChainflow/celo

branch : master

created branch time in 10 days

created repositoryChainflow/celo

created time in 10 days

MemberEvent
MemberEvent

issue commentcelo-org/celo-monorepo

Validator explorer group uptime issues

  1. There is no explanation for all the metrics that are shown in simple words for newcomers. An info pop-up can be really useful.
  2. The percentages listed in the three votes columns are very confusing and I feel don't give any insight about the validator

image

I agree that tooltips or something like that explaining each metric would be very helpful.

mrsmkl

comment created time in 11 days

issue commentcelo-org/celo-monorepo

Validator explorer group uptime issues

Can someone please point me to the uptime calculation?

mrsmkl

comment created time in 11 days

issue commentlivepeer/Grant-Program

Livepeer business case development grant application

@nelsorya Yes, we'll post to the forum and share in the orchestrator channel by Monday.

chris-remus

comment created time in 18 days

push eventchris-remus/chainflow

Chris Remus

commit sha 6e3068f63a727a45079e51754f30dc910acb4b5e

Update solana-validator-up-alert.sh

view details

push time in 22 days

push eventchris-remus/chainflow

Chris Remus

commit sha 31403f0d0a5d40dab5ffe2af78a3805f9403ce5e

Update solana-validator-monitoring.sh

view details

push time in 22 days

issue commentlivepeer/Grant-Program

Livepeer business case development grant application

Fantastic @nelsorya, we'll get started!

chris-remus

comment created time in a month

pull request commentnucypher/validator-profiles

Add Chainflow profile

@mswilkison Done!

chris-remus

comment created time in a month

push eventChainflow/validator-profiles

Chris Remus

commit sha b922d88f2ac8972324999e8cd2cb3fed9f35f657

Update profile.json

view details

push time in a month

issue commentlivepeer/Grant-Program

Livepeer business case development grant application

@nelsorya here are our suggested milestones, assuming we get approval to start by Friday, May 8 -

  • Scope by May 15
  • Phase 1 by June 7
chris-remus

comment created time in a month

issue commentlivepeer/Grant-Program

Livepeer business case development grant application

Thanks for the clarification @nelsorya. @glebdudka and I will get back to you on milestones today.

chris-remus

comment created time in a month

push eventchris-remus/GameOfZones

Chris Remus

commit sha 2a085e713155fa8f9532831e115e19c2e95a3dc4

Update staking-defense-phase-1.json

view details

push time in a month

push eventchris-remus/GameOfZones

Chris Remus

commit sha 85ef91bc77d4a45b0990bfff70255fee74173919

Update chainflow-phase-1.json

view details

push time in a month

push eventchris-remus/GameOfZones

Chris Remus

commit sha 3d1722d06af24847571b5522c456fa7c1823b27b

Update and rename chainflow.json to chainflow_phase_1.json

view details

push time in a month

push eventchris-remus/GameOfZones

Chris Remus

commit sha 29c6f0e81321c5da651b3989c4a534e98cb70dab

Update and rename chainflow.json to chainflow-phase-1.json

view details

push time in a month

PR opened cosmosdevs/GameOfZones

Create staking-defense-phase-1.json
+4 -0

0 comment

1 changed file

pr created time in a month

push eventchris-remus/GameOfZones

Chris Remus

commit sha f06cf6b23ca92ceb9d54a24135b0c2107b78d47f

Create staking-defense-phase-1.json

view details

push time in a month

fork chris-remus/GameOfZones

Welcome to Game of Zones. The Incentivized IBC Testnet.

fork in a month

push eventChainflow/net

Chris Remus

commit sha 4bf2e37f7b469c47f836f23941cab5baca4396eb

Update chainflow-gentx.json

view details

push time in a month

PR opened ovrclk/net

Create chainflow-gentx.json
+1 -0

0 comment

1 changed file

pr created time in a month

push eventChainflow/net

Chris Remus

commit sha 7a31198276b175ac51f0d39bad13b9ba4bd6be40

Create chainflow-gentx.json

view details

push time in a month

startedovrclk/akash

started time in a month

PR opened nucypher/validator-profiles

Add Chainflow profile
+144 -0

0 comment

2 changed files

pr created time in a month

push eventChainflow/validator-profiles

Chris Remus

commit sha 50d020370ac89a5571082948caed23c8e86ae2f0

Update profile.json

view details

push time in a month

push eventChainflow/validator-profiles

Chris Remus

commit sha 9dbb7653b3b301ecdc8a2f9ffad905e1139fb0c2

Update README.md

view details

push time in a month

push eventChainflow/validator-profiles

Chris Remus

commit sha 32659c4a9b949faac16f06dec6f689ff8b7b6639

Update README.md

view details

push time in a month

push eventChainflow/validator-profiles

Chris Remus

commit sha e83d74c15a5044d75752a800d1afd1f1b4d7c0b2

Update README.md

view details

push time in a month

push eventChainflow/validator-profiles

Chris Remus

commit sha 21646fe4b67a2d0d01f55398a9a04a5d432f6e03

Create README.md

view details

push time in a month

push eventChainflow/validator-profiles

Chris Remus

commit sha b1b125d5328490b6375b1878516c6a5239b84102

Create profile.json

view details

push time in a month

PR opened cosmosdevs/GameOfZones

add chainflow and staking defense
+8 -0

0 comment

2 changed files

pr created time in a month

push eventChainflow/GameOfZones

Chris Remus

commit sha 153d05ac35066b3b5bd7ba5e74cb850d1fe93cd7

Update staking-defense.json

view details

push time in a month

push eventChainflow/GameOfZones

Chris Remus

commit sha c446bf02857b60b20f9ea7b4ffb859465e5e52c8

Create chainflow.json

view details

push time in a month

push eventChainflow/GameOfZones

Chris Remus

commit sha 20403431e2e8c9b337f415b592a20c4ed9c54620

Create staking-defense.json

view details

push time in a month

push eventChainflow/cosmos-validator-mission-control

Chris Remus

commit sha ca26bbe172f71aa3895aedb425462d4980410a1b

Create README.md

view details

Chris Remus

commit sha 8079a912ebe15f5c7f2ad2c1a3b5672d347cefd5

Update README.md

view details

Chris Remus

commit sha 3b1da8fc043cfb42cb767487fc2ea34030f07c08

Update README.md

view details

Chris Remus

commit sha 1074e8fdd29a381bb4de95ec7ebfcf1861d368ca

Update README.md

view details

Chris Remus

commit sha 1a774880de65f5ac1f48d370399f201a27c2618f

Update README.md

view details

Chris Remus

commit sha 36c9342c08f13e43165245c1f45507417b21ba2b

Update README.md

view details

Chris Remus

commit sha 5a3fcc30dec2f93ad68d223bac7893d8d3d77b20

Update README.md

view details

Chris Remus

commit sha 91ef30a54739029e24e5fcdb86d919a9990990de

Update README.md

view details

Chris Remus

commit sha 4e48f9ea09d27ce9a17662db6321082804a1204b

Update README.md

view details

Chris Remus

commit sha 0ac7587fe2301ca1bf3b8e76a1be824870f66785

Update README.md

view details

Chris Remus

commit sha 59ab4a3ad4ace2a8a81df0611489343720cff032

Update README.md

view details

Chris Remus

commit sha ea5e1d7c0ba1a403345c5087051ad02e30d0380c

Update README.md

view details

Akshay

commit sha 36e615dc1ef78acb7556381fe663edb1107ec3d3

* Initial Structure and 13+ monitors implemented (Repetition needs to be removed for commands/endpoints fetching from same source) (Storing time-series data to db needs to be done) (Alerting needs to be implemented) Signed-off-by: Ironhide <ksh.gupt1@outlook.com>

view details

Akshay

commit sha 19c38c2600a99cf7ab6813085d0b0b8faeed9321

* Shifted from monitor domain to target domain with code restructuring! Signed-off-by: Ironhide <ksh.gupt1@outlook.com>

view details

Anil Kumar Kammari

commit sha 16a1d72c3ce589f90a75dc40c978e514e0fba6f9

Create README.md

view details

Akshay

commit sha c4f5cb664dc11715d99b1e14d7d4443beb7b902e

Alerting module added Implemented telegram alerts Signed-off-by: Ironhide <ksh.gupt1@outlook.com>

view details

Akshay

commit sha 45ddb066f4107a8baf52b3c36ae1b1181594d499

Added example.config.toml Signed-off-by: Ironhide <ksh.gupt1@outlook.com>

view details

anilCSE

commit sha 515fe8bac0a2896193e7c3e50056bcf1598ea460

Merge branch 'master' of github.com:chris-remus/chainflow-vitwit into vcf-targets-alerts

view details

Akshay

commit sha 7bb424b7eb0a6e198201de66143975746f9508b6

* Changed ReadFromTomlFile() -> ReadFromFile() Signed-off-by: Ironhide <ksh.gupt1@outlook.com>

view details

Akshay

commit sha 16817ad2236c89e2033dbab8a1bf70544d48c811

* Dockerfile added Signed-off-by: Ironhide <ksh.gupt1@outlook.com>

view details

push time in a month

MemberEvent

create barnchChainflow/cosmos-validator-mission-control

branch : master

created branch time in a month

created repositoryChainflow/cosmos-validator-mission-control

Cosmos validator mission control monitoring and alerting tool.

created time in a month

push eventchris-remus/cosmos-validator-mission-control

Akshay

commit sha 36e615dc1ef78acb7556381fe663edb1107ec3d3

* Initial Structure and 13+ monitors implemented (Repetition needs to be removed for commands/endpoints fetching from same source) (Storing time-series data to db needs to be done) (Alerting needs to be implemented) Signed-off-by: Ironhide <ksh.gupt1@outlook.com>

view details

Akshay

commit sha 19c38c2600a99cf7ab6813085d0b0b8faeed9321

* Shifted from monitor domain to target domain with code restructuring! Signed-off-by: Ironhide <ksh.gupt1@outlook.com>

view details

Anil Kumar Kammari

commit sha 16a1d72c3ce589f90a75dc40c978e514e0fba6f9

Create README.md

view details

Akshay

commit sha c4f5cb664dc11715d99b1e14d7d4443beb7b902e

Alerting module added Implemented telegram alerts Signed-off-by: Ironhide <ksh.gupt1@outlook.com>

view details

Akshay

commit sha 45ddb066f4107a8baf52b3c36ae1b1181594d499

Added example.config.toml Signed-off-by: Ironhide <ksh.gupt1@outlook.com>

view details

anilCSE

commit sha 515fe8bac0a2896193e7c3e50056bcf1598ea460

Merge branch 'master' of github.com:chris-remus/chainflow-vitwit into vcf-targets-alerts

view details

Akshay

commit sha 7bb424b7eb0a6e198201de66143975746f9508b6

* Changed ReadFromTomlFile() -> ReadFromFile() Signed-off-by: Ironhide <ksh.gupt1@outlook.com>

view details

Akshay

commit sha 16817ad2236c89e2033dbab8a1bf70544d48c811

* Dockerfile added Signed-off-by: Ironhide <ksh.gupt1@outlook.com>

view details

Ironhide

commit sha ad21a77eb445413cb360caf5dd1fd37350c2df6d

Merge branch 'vcf-targets-alerts' of https://github.com/chris-remus/chainflow-vitwit into vcf-targets-alerts

view details

Akshay

commit sha 291c9339a486799ed0d2a6922de4cbe82876d6e6

* changed README.md Signed-off-by: Ironhide <ksh.gupt1@outlook.com>

view details

Akshay

commit sha bf410b639812394018f2a8e65a22cd05acd4c33a

* Added runner to run functions * Bug fix in telegram alert (msg variable not used) Signed-off-by: Akshay Gupta <akshaydotsh@gmail.com>

view details

Akshay Gupta

commit sha 880a00ce02a67698278bca6551cd156c615868e2

* Email Alerting Signed-off-by: Akshay Gupta <akshaydotsh@gmail.com>

view details

Akshay Gupta

commit sha 1b0778ff3203ea5e289161eb29a3ec065ae9f227

* changed check for gaiad running from endpoint to cmd line Signed-off-by: Akshay Gupta <akshaydotsh@gmail.com>

view details

Akshay Gupta

commit sha 6a6a04d273d07177532d0f4111be1992daf04300

* README.md email alerting Signed-off-by: Akshay Gupta <akshaydotsh@gmail.com>

view details

Akshay Gupta

commit sha 71dd3e8f4e5b7b22ea2de902a8d16a35a4516fb8

* prometh client for gaiad status * config change for scraper Signed-off-by: Akshay Gupta <akshaydotsh@gmail.com>

view details

Akshay Gupta

commit sha 0bdfde58b61b1b5a6c6444f65bf21047e1d2a970

* Prom Metric -> no. of peers Signed-off-by: Akshay Gupta <akshaydotsh@gmail.com>

view details

Akshay Gupta

commit sha cd9f52cff7b2e74f6de0aa49998eee5ec22929f7

printf bug fix Signed-off-by: Akshay Gupta <akshaydotsh@gmail.com>

view details

Akshay Gupta

commit sha 1bbcddd7513c922aaf66d8b49682b2f43c2b69cb

* Implemented influxDB for: - gaiad running/not runningA Signed-off-by: Akshay Gupta <akshaydotsh@gmail.com>

view details

Akshay Gupta

commit sha a9cdd15895396e61f58efd833c1ac1e0bf469fcb

* Num of peers & Peer Addresses with InfluxDB Signed-off-by: Akshay Gupta <akshaydotsh@gmail.com>

view details

Akshay Gupta

commit sha f7a742b7975ecab48cac14a6adffdc86f5606fe6

* Metrics from gaiacli status added with influxDBA Signed-off-by: Akshay Gupta <akshaydotsh@gmail.com>

view details

push time in a month

push eventchris-remus/cosmos-validator-mission-control

Chris Remus

commit sha 387d7e574ea06cdd42517d7bf1204174b7917494

Update README.md

view details

push time in a month

push eventchris-remus/cosmos-validator-mission-control

Chris Remus

commit sha 7643419d63cb6cf37fa54bd22d0078b947a5c5db

Update README.md

view details

push time in a month

push eventchris-remus/cosmos-validator-mission-control

Chris Remus

commit sha 0a11171157a50b482bf7dbafb42c4547fb5d3b26

Update README.md

view details

push time in a month

push eventchris-remus/cosmos-validator-mission-control

Chris Remus

commit sha e32c50ebf142b3d9994f76e92df62610d17ed112

Add files via upload

view details

push time in a month

push eventchris-remus/cosmos-validator-mission-control

Chris Remus

commit sha 6adb6f6dcc47dbe9f7567c65da8f139faf2ae34e

Update README.md

view details

push time in a month

push eventchris-remus/cosmos-validator-mission-control

Chris Remus

commit sha dc8897a4890d761cf2033e0b80344e8450b8b935

Update README.md

view details

push time in a month

push eventchris-remus/cosmos-validator-mission-control

Chris Remus

commit sha 5b56abae095dbec6c96d7312b896edc90a244841

Update README.md

view details

push time in a month

issue commentlivepeer/Grant-Program

Livepeer business case development grant application

@nelsorya 1-4 look good. Let's leave 5 open, as it's probably part of a longer discussion. For example, we'd need to clearly define what "maintenance" is.

Rather than delay kicking this off any further, I'd suggest we proceed with 1-4, with an agreement that we'll maintain it under mutually agreeable terms.

How does that sound?

chris-remus

comment created time in a month

issue commentlivepeer/Grant-Program

Livepeer business case development grant application

@nelsorya & @adamsoffer do you have an ETA on the suggested metrics? We're ready to get rolling on this!

chris-remus

comment created time in a month

push eventchris-remus/chainflow-icf-validator-tool-grant

Chris Remus

commit sha a73f3267eb14f123efafacf6a2fd9ac3f961c644

Update README.md

view details

push time in a month

push eventchris-remus/testnets-2

Chris Remus

commit sha d68463c8acd3207e193afc7856021286878140e1

Delete README.md

view details

push time in 2 months

push eventchris-remus/testnets-2

Chris Remus

commit sha 2dbf074ff6cfae7b8ee778f4d4594e4e5cc38130

Delete chainflow-kontraua-gentx.json

view details

push time in 2 months

push eventchris-remus/testnets-2

Chris Remus

commit sha 57708fad336b9145c3257a460b165002e00a7d4f

Update chainflow.json

view details

push time in 2 months

fork chris-remus/celo-monorepo

Official repository for core projects comprising the Celo platform

https://celo.org

fork in 2 months

push eventchris-remus/testnets-2

Chris Remus

commit sha 0dedb7c234189375571f61f3ce1a2910be3ab7c1

Update chainflow.json

view details

push time in 2 months

PR opened regen-network/testnets

add chainflow.json
+13 -0

0 comment

3 changed files

pr created time in 2 months

push eventchris-remus/testnets-2

Chris Remus

commit sha 9ef4263bf7fc62accf6dc1cd347fac0a1d974ece

Create chainflow.json

view details

push time in 2 months

issue commentlivepeer/Grant-Program

Livepeer business case development grant application

@nelsorya Could we schedule a brief call to finalize the details?

chris-remus

comment created time in 2 months

issue commentlivepeer/Grant-Program

Livepeer business case development grant application

@nelsorya To clarify, would this be 10 different parties engaging or a total of 10 engagements, e.g. 5 conversations with at least 2 responses?

In addition to your list of engagement forums, I'd add forum.livepeer.org as well.

Also, would you consider tiers, e.g. 50% of the grant for 5 conversations, 100% for 10 engagements and maybe a 25% bonus for over 20 engagements?

chris-remus

comment created time in 2 months

issue commentchris-remus/chainflow-icf-validator-tool-grant

Identify tool combinations to implement the spec

It turns out that Icinga was unnecessary, as we were able to customize Grafana/Prometheus to send the alerts we needed to send.

chris-remus

comment created time in 2 months

MemberEvent

PR opened regen-network/testnets

Create Phase-3_Chainflow.json
+4 -0

0 comment

1 changed file

pr created time in 2 months

push eventchris-remus/testnets-2

Chris Remus

commit sha 4e12e0c56bf3970b7a1ff8491e7073c49a2ee625

Create Phase-3_Chainflow.json

view details

push time in 2 months

issue commentlivepeer/Grant-Program

Livepeer business case development grant application

@adamsoffer that's fantastic news!

Regarding your questions -

Is the idea to continue iterating on the spreadsheet? We think this would be a good tool to make accessible via the web — easier to share, discover, and measure usage/success. Of course, if this is out of scope for the 40 hours that can be made into a separate grant.

Yes, that's the idea for this proposal. Once we finish this phase and agree on what the updated spreadsheet looks like, we can create a web version of it, under a separate grant.

Is there a metric you’d like to use for measuring the success of this proposal?

I'll discuss this with Gleb and get back to you soon 👍

chris-remus

comment created time in 2 months

IssuesEvent

issue closedchris-remus/chainflow-icf-validator-tool-grant

Implement alerting

1 Availability

  • [x] 1.1 Server available and reachable
  • [x] 1.2 Gaiad running
  • [x] 1.3 Validator active, i.e. not jailed

2 Performance

  • [ ] 2.1. Disk utilization
  • [ ] 2.3 CPU utilization
  • [ ] 2.4 RAM utilization

3 Validator performance

  • [x] 3.3 Caught-up?
  • [x] 3.4 Validator voting?
  • [x] 3.5 Missed blocks

4 Connectivity

  • [x] 4.1. Number of peers

5 Validator details

  • [x] 5.8 Voting power

6 Proposals

  • [x] 6.1 New proposal
  • [x] 6.2.2 Proposal voting period and period expiration date
  • [x] 6.2.3 Validator voting status

closed time in 2 months

chris-remus

PR opened regen-network/testnets

Create chainflow.json
+17 -0

0 comment

1 changed file

pr created time in 2 months

push eventchris-remus/testnets-2

Chris Remus

commit sha 49df2717f36c31ed69a5c9599b161981f3232263

Create chainflow.json

view details

push time in 2 months

issue openedlivepeer/Grant-Program

Livepeer business case development grant application

Give a 3 sentence description about this proposal.

Chris from Chainflow and Gleb from StakingRewards have recently open-sourced a Livepeer Orchestrator and Network Model (link). This grant proposal is directed to receiving support for extending the model in terms of depth, interactivity and outcome, based on some add-on features listed in the chapters below.

This model can be used by various demand- and supply-side actors to make data-driven decisions around e.g. pixel pricing and demand forecasting. The goal is not only to improve but also to maintain the model over time which can be reflected in the grant's structure (see Scope).

Describe the problem you are solving.

While building up a business case for an Orchestrator we came to realize that there is a lack of resources and models which can be used to make data-driven decisions when participating in Livepeer today. These would require a combination of demand-side estimations/observations (demand for transcoding, pixel price competitiveness compared to legacy actors, etc.) and supply-side parameters (network-related data, pricing, breakeven pixel cost given a particular Orchestrator set-up, etc.).

Given the network's relatively young age and the speed the space as a whole is moving as well as additional complexity of extremely multi-variate pixel pricing, creating such a model has posed a significant challenge and requires multiple iterations and assumption validation rounds with industry experts.

Having additional significant improvement to the flexible, adjustable and scenario-based model like that will save time to many ecosystem participants as well as allow them to come up with own strategies, be it staking, transcoding, hodling, etc.

Describe the solution you are proposing.

The solution we are proposing is to build upon the first model and get it to a certain level of maturity in terms of breadth of scenarios and benchmarks, depth and validation of certain assumptions, as well as improve the data and outcome interpretation side by implementing a set of features (see Scope).

This model can be used by a variety of Livepeer ecosystem participants to drive their data-driven decision-making:

  1. Demand-side actors, like video streamers and potential partners to estimate and compare costs/prices between Livepeer and various centralized alternatives.

  2. Supply-side actors, either existing or future Orchestrators to calculate the business case of operating one and figuring out the fees to charge as well as existing miners considering dedicating some rigs to Livepeer. Or the token holders and/or investors to calculate their expected LPT+ETH rewards.

  3. Ecosystem in general to model the effects of certain updates on the network, evaluate the impact of governance decisions, etc.

Describe the scope of the project including a rough timeline and milestones

Here are some feature and improvement ideas which will become deliverables were we to receive the grant (further scoping with the community is desirable):

  • Dashboard showing/summarizing the data interpretation of each outcome (e.g. is this pixel price competitive, should operations be outsourced, at which point an orchestrator should or needs to scale up its operation, etc.)
  • Modelling of total network yield (LPT+ETH) in relation to external staking and DeFi opportunities and how it impacts participation (not regarding LPT as an isolated network)
  • Additional centralized benchmarks based on geographies (additional scenarios)
  • Overall improvements, adding new parameters and orchestrator business-related considerations (e.g. marketing expenses, etc.)
  • Other suggestions from the community are welcome.

Feature shortlisting to 3-6 features and their priorization is expected to be made/proposed with a help of e.g. community voting/poll on most desired features. These features will be then taken into account for scoping the following feature sets:

Limited set of features (3 man-days / 24 hours)* - deliverable within 2-4 weeks of grant allocation and/or feature vote close

Comprehensive set of features (3-5 man-days / 24-40 hours)** - deliverable within 4-6 weeks of grant allocation and/or feature vote close

*limited set of features would mean 1-3 added features from the feature list based on 3 man-day effort estimations of scope. Limited scope also means an incremental improvement in model capabilities and outcome detail.

**comprehensive set of features would mean 2-3 further features from the feature list based on further 3-5 man-day effort. Full scope also means a significant improvement in model capabilities and outcome detail.

Please estimate hours spent on project based on the above

The estimated hours can be seen in the chapter above. TLDR: Limited set of features (3 man-days / 24 hours); Comprehensive set of features (3-5 man-days / 24-40 hours)

Effort estimations are kept smaller intentionally, given the fact that the size of the grant is limited. We would however expect that depending on the feature sets, the overall effort can exceed the estimate, in which case the addressing the surplus may be addressed via subsequent grant applications.

created time in 3 months

PR opened regen-network/testnets

add-chainflow-kontraua-gentx
+2 -0

0 comment

2 changed files

pr created time in 3 months

push eventchris-remus/testnets-2

Chris Remus

commit sha 5e6206b979781537680bb0600c64d2f90e17b8e9

Create chainflow-kontraua-gentx.json

view details

push time in 3 months

issue openedchris-remus/chainflow-icf-validator-tool-grant

Implement 6 - Proposals

New proposal List of open proposals Proposal result

created time in 3 months

issue openedchris-remus/chainflow-icf-validator-tool-grant

Implement 3 - Validator Performance

Block time Current block height Caught up? (Y/N) Validator voting? (Y/N) Missed blocks

created time in 3 months

more