Skip to content

illustrate the decay regimes at 32 wallets - #39

Open
bc1cindy wants to merge 1 commit into
problem-definitionfrom
ctp-figure-32
Open

bc1cindy wants to merge 1 commit into
problem-definitionfrom
ctp-figure-32

Conversation

@bc1cindy

@bc1cindy bc1cindy commented Sep 25, 2026 •

Copy link
Copy Markdown
Member

superseeded #38

adds 32 wallet visualization of the decay, shipped as light and dark external svg files that the book paints per theme

the sources run along the rows and the rounds along the columns, with the same coin struck in both graphs

follow up

Captura de Tela 2026-09-24 às 22 39 25 Captura de Tela 2026-09-24 às 22 39 43 Captura de Tela 2026-09-24 às 22 44 18 Captura de Tela 2026-09-24 às 22 45 44 Captura de Tela 2026-09-24 às 22 45 58

besides that, there are the open title suggestions that @yuval-block asked for:

so to be a bit more precise i think the "collaborative transaction privacy" title is descriptive of the content, but it doesn't quite capture that in the context of this repo it defines the problem that we're trying to solve

and if we just emphasize problem definition for fungi, that sells short the applicability of this perspective to alternatives

so i think a good title would address both of these, whereas my current title and your proposed alternatives only focuses on the first function of this doc

suggestions:

  • The deanonymization problem in collaborative transactions
  • What collaborative transactions must not leak

any other?

Comment thread theme/diagrams.css Outdated
Comment thread theme/diagrams.css Outdated
@bc1cindy
bc1cindy force-pushed the ctp-figure-32 branch 2 times, most recently from 9c81510 to 897ff1b Compare September 27, 2026 15:35
@oakagent

oakagent commented Oct 1, 2026

Copy link
Copy Markdown

ACK 897ff1b (automated): reviewed 1 commit 897ff1b; no findings.

@bc1cindy
bc1cindy force-pushed the ctp-figure-32 branch 2 times, most recently from 897ff1b to 4b3b7a9 Compare October 8, 2026 02:11
Ten strikes leave twenty-two candidates against one.

Keep light and dark SVGs as separate files, referenced through a picture
in the Markdown source so the figure renders on GitHub.

During the mdBook build only, embed both SVGs into the generated HTML.
Select the version matching the book theme and use the light version
for printing, avoiding extra image requests and CSS backgrounds.
@oakagent

oakagent commented Oct 8, 2026

Copy link
Copy Markdown

ACK dc3faa7 (automated): reviewed 1 commit dc3faa7; no findings.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants