https://github.com/redgold-io/redgold

p2p database / compute engine & portfolio target models
https://github.com/redgold-io/redgold

compute crypto cryptocurrency database rust wasm

Last synced: 23 days ago
JSON representation

p2p database / compute engine & portfolio target models

• Host: GitHub
• URL: https://github.com/redgold-io/redgold
• Owner: redgold-io
• License: mit
• Created: 2023-05-07T20:20:55.000Z (almost 2 years ago)
• Default Branch: dev
• Last Pushed: 2024-09-13T04:03:12.000Z (7 months ago)
• Last Synced: 2024-09-14T14:44:30.577Z (7 months ago)
• Topics: compute, crypto, cryptocurrency, database, rust, wasm
• Language: Rust
• Homepage: https://redgold.io
• Size: 9.52 MB
• Stars: 16
• Watchers: 1
• Forks: 2
• Open Issues: 202
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE.md
  • Security: SECURITY.md

Awesome Lists containing this project

README

        
#  Redgold

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

![Dev](https://github.com/redgold-io/redgold/actions/workflows/ci.yml/badge.svg?branch=dev)

[Website](https://redgold.io) |

[Contributing](https://dev.docs.redgold.io/contribute/guide) | 

[Dev Setup](https://dev.docs.redgold.io/contribute/dev-setup) | 

[Whitepaper](https://dev.docs.redgold.io/whitepaper/whitepaper) | 

[Run A Node](https://dev.docs.redgold.io/guides/node-setup) | 

[Security Procedures](https://dev.docs.redgold.io/introduction/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](https://arxiv.org/pdf/2108.05236.pdf) 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](https://dev.docs.redgold.io/whitepaper/whitepaper).

* This project is still in experimental development but has a live mainnet.