Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
CCS Proposals
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
xiphon
CCS Proposals
Commits
146039be
Commit
146039be
authored
5 years ago
by
hyc
Browse files
Options
Downloads
Patches
Plain Diff
Clarification of incremental funding structure
And some deadlines
parent
6b3e885d
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
RandomX-audit.md
+7
-1
7 additions, 1 deletion
RandomX-audit.md
with
7 additions
and
1 deletion
RandomX-audit.md
+
7
−
1
View file @
146039be
...
...
@@ -49,4 +49,10 @@ to CHF and EUR). The request is for 1400 XMR, using an exhange estimate of 1 XMR
the funding is in fiat currency, this amount will be updated to reflect price fluctuations
until funded.
The reviews will be funded in this order as soon as sufficient funds are available.
The reviews will be funded in this order as soon as sufficient funds are available. This means
that as soon as enough funds have been raised to pay for Kudelski we will engage them to begin
their review. If/when sufficient funds are raised to pay for X41 we will start that; if/when
sufficient additional funds are raised to cover QuarksLab we will start that. If we don't raise
enough funds to cover all 3 reviews we will go with whatever we can cover. Reviews must be
completed by end of June so that any identified problems can be fixed by July, and ready for
a code freeze and subsequent October release.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment