redgold
| Crates.io | redgold |
| lib.rs | redgold |
| version | |
| source | src |
| created_at | 2022-06-15 02:46:36.42193+00 |
| updated_at | 2025-02-28 22:59:41.927699+00 |
| description | Decentralized Portfolio Contracts & Data Lake |
| homepage | https://redgold.io |
| repository | https://github.com/redgold-io/redgold |
| max_upload_size | |
| id | 606218 |
| Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
(sergei-pq)
documentation
README
Redgold
Website | Contributing | Dev Setup | Whitepaper | Run A Node | Security Procedures
Redgold is a crypto portfolio contract platform designed around data lake transforms and executors. Uses multiparty native contracts for asset management. Primary use case is ETFs & Portfolio target models (expressing a desired portfolio allocation as a function and having validators automatically fulfill it,) but the platform is designed to be general purpose as a decentralized data lake and relational algebra compute engine for crypto related contracts.
Heavily inspired by Spark and pandas/polars like data transformations on conventional parquet data lakes, with the key distinguishing factor being the ability to support multi-tenant compute with arbitrary secure UDFs compiled by anyone. WASM executors are used for secure remote code execution to chain together transforms operating on SQL-like data loading functions as inputs. Protobuf is used for relational algebra descriptors and for raw signature operations and requests. Arrow is used as a cross-memory format for WASM invocations, with sqlite tables for frequent access and parquet tables for long-lived data indexes. All operations are translated to work with Kademlia distances. ACCEPT consensus protocol is the most similar to the demonstrated primary optimization technique. For a full technical description and motivation of this project please refer above to the whitepaper.
-
This project is still in experimental development but has a live mainnet.