Skip to content

chore: update repository URLs to use OrderBookTrade #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
libaice merged 1 commit into from
Apr 13, 2026
Merged

chore: update repository URLs to use OrderBookTrade #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@ version = "0.1.0"
edition = "2021"
description = "Detect ghost fills on Polymarket CLOB"
license = "MIT"
repository = "https://github.com/libaice/GhostGuard"
homepage = "https://github.com/libaice/GhostGuard"
repository = "https://github.com/OrderBookTrade/GhostGuard"
homepage = "https://github.com/OrderBookTrade/GhostGuard"
keywords = ["polymarket", "ghost-fill", "clob", "polygon", "trading"]
categories = ["command-line-utilities", "cryptography::cryptocurrencies"]
readme = "README.md"
Expand Down
4 changes: 2 additions & 2 deletions docs/ghost-fills-polymarket.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,7 @@ The only invariant across all variants: **the on-chain settlement transaction re

## Part 4: GhostGuard

I built [GhostGuard](https://github.com/OrderBookTrade/ghostguard) to detect ghost fills by verifying every CLOB fill on-chain. It doesn't care how the attack happened. It checks whether the fill actually settled.
I built [GhostGuard](https://github.com/OrderBookTrade/GhostGuard) to detect ghost fills by verifying every CLOB fill on-chain. It doesn't care how the attack happened. It checks whether the fill actually settled.

### Core logic

Expand Down Expand Up @@ -407,7 +407,7 @@ v1 solves the critical problem: knowing that a ghost happened, in time to react.

## Links

- **GhostGuard**: [github.com/OrderBookTrade/ghostguard](https://github.com/OrderBookTrade/ghostguard)
- **GhostGuard**: [github.com/OrderBookTrade/GhostGuard](https://github.com/OrderBookTrade/GhostGuard)
- **Known ghost fill tx**: [0x9e3230ab...on Polygonscan](https://polygonscan.com/tx/0x9e3230abde0f569da87511a6f8823076f7b211bb00d10689db3b7c50d6652df0)
- **CTF Exchange contract**: [0x4bfb41d5...on Polygonscan](https://polygonscan.com/address/0x4bfb41d5b3570defd03c39a9a4d8de6bd8b8982e)

Expand Down
4 changes: 2 additions & 2 deletions ghostguardup
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@
set -euo pipefail

# ghostguardup — installer for GhostGuard CLI
# Usage: curl -L https://raw.githubusercontent.com/libaice/GhostGuard/main/ghostguardup | bash
# Usage: curl -L https://raw.githubusercontent.com/OrderBookTrade/GhostGuard/main/ghostguardup | bash

REPO="libaice/GhostGuard"
REPO="OrderBookTrade/GhostGuard"
INSTALL_DIR="${GHOSTGUARD_INSTALL_DIR:-$HOME/.ghostguard/bin}"
BASE_URL="https://github.com/${REPO}/releases/latest/download"

Expand Down
Loading