c03rad0r
Your local ISP
The coordinator proposals from SatsAndSports give instant refunds but require
the coordinator to hold a Cashu signing key and the seller to need the
coordinator's signature at settlement.
The coordinator proposals from SatsAndSports give instant refunds but require
the coordinator to hold a Cashu signing key and the seller to need the
coordinator's signature at settlement.
The coordinator proposals from SatsAndSports give instant refunds but requirethe coordinator to hold a Cashu signing key and the seller to need thecoordinator's signature at settlement.
The coordinator proposals from SatsAndSports give instant refunds but require
the coordinator to hold a Cashu signing key and the seller to need the
coordinator's signature at settlement.
Open questions
What should minimum_extension default to? Something small like 5 minutes seems right — enough for a response but not so large that a single bid adds hours.
What should settlement_grace_period be? The current AUCTION_SETTLEMENT_GRACE_SECONDS is 3600 (1 hour), which is very conservative. With the moving bound, the grace period directly adds to the auction duration (each bid extends by grace + minimum_extension ). However, if a collaborative close mechanism exists, the grace period becomes a worst-case fallback rather than the normal refund path. In the common case (seller online), losing bidders get fast refunds via collaborative close regardless of the grace period length. This means a longer grace period could be used for safety (handling seller downtime, mint downtime) without penalizing losing bidders in the normal case. The right value depends on whether collaborative close is part of the design.
Should there be an absolute maximum duration? Even with the moving bound, an auction could theoretically run for weeks if bids keep arriving. A very generous absolute cap (e.g., 7 days from start_at ) might be worth considering as a safety net.
How does this interact with the existing AUCTIONS.md codex? Section 6.1 explicitly states "Without a hard upper bound, anti-sniping is not acceptable." This proposal replaces the hard upper bound with a moving bound — the codex would need updating.
Locktime oracle enforcement: currently the client computes the locktime. With this design, the oracle must dictate it. This shifts trust slightly — the oracle could set an unreasonably short locktime. But the oracle is already trusted (it holds the derivation paths), so this is consistent with the existing threat model.
This setup blends old-school amateur radio resilience with modern digital capability, proving that robust communication doesn’t require high budgets — only ingenuity, open-source tools, and the will to stay connected when everything else fails.
🏁 Consider
For around $60, you can construct a self-contained ham radio data hotspot capable of email, APRS, SMS, and digital messaging over RF — no Internet, no cell towers, and no dependency on external infrastructure.
This setup blends old-school amateur radio resilience with modern digital capability, proving that robust communication doesn’t require high budgets — only ingenuity, open-source tools, and the will to stay connected when everything else fails.
This setup blends old-school amateur radio resilience with modern digital capability, proving that robust communication doesn’t require high budgets — only ingenuity, open-source tools, and the will to stay connected when everything else fails.
🏁 ConsiderFor around $60, you can construct a self-contained ham radio data hotspot capable of email, APRS, SMS, and digital messaging over RF — no Internet, no cell towers, and no dependency on external infrastructure.This setup blends old-school amateur radio resilience with modern digital capability, proving that robust communication doesn’t require high budgets — only ingenuity, open-source tools, and the will to stay connected when everything else fails.
This setup blends old-school amateur radio resilience with modern digital capability, proving that robust communication doesn’t require high budgets — only ingenuity, open-source tools, and the will to stay connected when everything else fails.
🏁 ConsiderFor around $60, you can construct a self-contained ham radio data hotspot capable of email, APRS, SMS, and digital messaging over RF — no Internet, no cell towers, and no dependency on external infrastructure.This setup blends old-school amateur radio resilience with modern digital capability, proving that robust communication doesn’t require high budgets — only ingenuity, open-source tools, and the will to stay connected when everything else fails.
This setup blends old-school amateur radio resilience with modern digital capability, proving that robust communication doesn’t require high budgets — only ingenuity, open-source tools, and the will to stay connected when everything else fails.
🏁 ConsiderFor around $60, you can construct a self-contained ham radio data hotspot capable of email, APRS, SMS, and digital messaging over RF — no Internet, no cell towers, and no dependency on external infrastructure.This setup blends old-school amateur radio resilience with modern digital capability, proving that robust communication doesn’t require high budgets — only ingenuity, open-source tools, and the will to stay connected when everything else fails.
This setup blends old-school amateur radio resilience with modern digital capability, proving that robust communication doesn’t require high budgets — only ingenuity, open-source tools, and the will to stay connected when everything else fails.
🏁 ConsiderFor around $60, you can construct a self-contained ham radio data hotspot capable of email, APRS, SMS, and digital messaging over RF — no Internet, no cell towers, and no dependency on external infrastructure.This setup blends old-school amateur radio resilience with modern digital capability, proving that robust communication doesn’t require high budgets — only ingenuity, open-source tools, and the will to stay connected when everything else fails.