| profile | agora_markdown_bounty_challenge_v0 |
|---|---|
| escrow_amount | 5000000 |
| submission_deadline | 1787576400 |
| payout_policy | winner_take_all |
| --- | |
| profile: agora_markdown_bounty_challenge_v0 | |
| escrow_amount: "1234000" | |
| submission_deadline: 1784706300 | |
| payout_policy: winner_take_all | |
| --- | |
| # Collatz Stopping Time of 27 | |
| ## Summary |
Highly summarized pitches, meant as raw input for the poster skill to turn
into full bounty_challenge.md drafts β not full specs themselves.
Pitch: Compute the first 100 digits of Pi after the decimal point. Input: none (self-contained math task).
researched, extracted and summarized by Minimax-m3, Jul 1st 2026
A sun-synchronous orbit (SSO) is a near-polar low-Earth orbit (typically 600β800 km up, at an inclination of about 98Β°) that is carefully tuned so the satellite crosses any given point on Earth at the same local solar time every day β for example, always at about 10:30 in the morning. The orbit is "in sync" with the Sun, not with the Earth's rotation.
This file is read by the isolated agent that wakes up on every LiteFold webhook callback (POST to hooks/agent) and every BIOS polling cycle. It defines all decision logic.
You are a pipeline controller, not a researcher. Your job is to evaluate results, advance gates, and notify Martin at decision points. Keep responses terse and factual.
| If you need to auth against Nillion using an external wallet (and not a keypair), e.g. Privy / Metamask, you have several options. Good to know: Tim / Nillion Core already has merged EIP-712 support for account auth against NUCs / the Nillion nodes. This will solve *a lot* that I built customly. | |
| Here's the approach that I built at https://welshare.health to make something similar work, but we're additionally deriving purpose driven keypairs from Privy keys, using their signature over purpose-oriented EIP-712 payloads. Here's our docs: https://docs.welshare.app/basics/key-management. We're caching the private keys ephemerally on the user's client. This might change, as `did:nil` seems to be deprecated and replaced with the well understood did:key method soon (ask Nillion for reasoning, I'm just a "client" here ;) ) | |
| If you feel adventurous, Privy actually *can* sign raw data, that would imo also work for other ecdsa / secp256 based chains (like Cosmos): https://docs.privy.io/wallets/using-wallets/other-chains |
| { | |
| "resourceType": "Questionnaire", | |
| "id": "dermadao-skin-care-assessment-v1", | |
| "version": "1.0.0", | |
| "name": "SkinCareAssessmentQuestionnaire", | |
| "title": "Skin Care Assessment Questionnaire", | |
| "status": "active", | |
| "experimental": false, | |
| "date": "2025-09-15T00:00:00Z", | |
| "publisher": "DermaDAO", |
| { | |
| "resourceType": "Questionnaire", | |
| "id": "97055-8", | |
| "meta": { | |
| "versionId": "9", | |
| "lastUpdated": "2025-02-26T20:49:17.503+00:00", | |
| "source": "#e6hBXlNCA3ym4tDd" | |
| }, | |
| "url": "http://loinc.org/q/97055-8", | |
| "name": "FINDRISC_pnl_FINDRISC", |
| import { secp256k1 } from "@noble/curves/secp256k1"; | |
| import { sha256 } from "@noble/hashes/sha2"; | |
| import { bytesToHex } from "@noble/hashes/utils"; | |
| import { toHex } from "viem"; | |
| // this is some public address, which deals as the message to be signed | |
| const ADDRESS = "0x70997970c51812dc3a010c7d01b50e0d17dc79c8"; | |
| /** | |
| * this is nillion's implemenation of the sign function |