Oracle3
Oracle3: 예측시장 거래 엔진·MCP 서버
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Non-custodial bitcoin donations for charities and non-profits. Product brief in project-brief.md, technical design in docs/design.md, stack in docs/stack.md, plan in ROADMAP.md, brand in brand/README.md.
Under active development; not ready for live donation operations. Hosted and self-hosted deployments use this same codebase. Publishing the source does not mark a production release.
With Node 22.12+, pnpm and Docker installed:README 전문 보기 ↗Non-custodial bitcoin donations for charities and non-profits. Product brief in project-brief.md, technical design in docs/design.md, stack in docs/stack.md, plan in ROADMAP.md, brand in brand/README.md.
Under active development; not ready for live donation operations. Hosted and self-hosted deployments use this same codebase. Publishing the source does not mark a production release.
With Node 22.12+, pnpm and Docker installed:
pnpm install --frozen-lockfile
pnpm demo
This starts an isolated database, seeds Harbour Aid, and serves the dashboard and an embedded donation page. No real funds or outgoing email are involved. Follow the five-minute walkthrough.
/app/setup: saved progress, mainnet wallet address verification, email sender, allowed website origins and an installation snippet.Still to build: live chain detection, a real fresh-wallet history check, historical exchange-rate sourcing, and the continuously running worker. Production can issue real addresses but does not yet detect or value incoming bitcoin. Further launch and product work is tracked in the roadmap.
apps/web Astro site and app (Node or Netlify adapter)
packages/core Domain logic, schema, adapters. No framework imports.
packages/widget Embeddable web component
corepack enable # pnpm
pnpm install
cp .env.example .env # configure auth and encryption keys
docker compose up -d db # Postgres on :5432
pnpm --filter @satsrecord/core db:migrate
pnpm dev # http://localhost:4321
pnpm test # core tests, in-process Postgres, no Docker needed
pnpm build && pnpm start # production server
compose.yaml is for local development only: its database and web ports bind to 127.0.0.1, and its credentials are public development defaults. Do not use it as a production configuration.
Hosted is invite-only. Put your address in OPERATOR_EMAILS, sign in at /login, and issue invites from /admin. OPEN_SIGNUP=true enables /signup instead.
For a separate seeded demo organisation in an existing development environment, enable SIMULATE_DONATIONS=true, sign in, and visit /dev/dashboard. Owners and admins can use /dev/donations to simulate a payment against an issued address, record a fixed-rate valuation and send an acknowledgement. The widget then shows received. Simulation routes are unavailable in production builds.
With the console mailer, DEV_OUTBOX=true and a separate DEV_OUTBOX_PASSWORD of at least 32 characters enable the protected local outbox at /dev/outbox.
Testing checklists: onboarding, dashboard, widget, simulation.
Netlify builds apps/web using the checked-in netlify.toml. Keep the base directory at the repository root and set the package directory to apps/web. The build applies database migrations before building the app. See production configuration for environment variables and notification scheduling.
The Dockerfile builds the same app with the Node adapter for self-hosting. The standalone production Compose configuration requires your own secrets, keeps Postgres private, and exposes the web server only to a reverse proxy on the host. Follow the self-hosting guide for setup, current limitations, backups and upgrades.
Netlify preview and branch builds are disabled by default. Production secrets must also be restricted in Netlify's settings; repository configuration alone cannot protect them from a modified pull request.
Report vulnerabilities privately using SECURITY.md. Maintainers should complete the publication checks before changing repository visibility.
Application: AGPL-3.0-only. Widget (packages/widget): MIT. Third-party components retain their own licences.