Bumblefudge

User feedback: No way to address a specific transaction

5

In the past, we've discussed block heights (whether as a new CAIP or as a "query parameter"). A more fundamental use case might be addressing across multiple namespaces a specific...

[CAIP-25] Proposed Use Case: Optional Requests for only accounts w/X DAI/Eth in them

1

@hmalik88 mentioned on call today, my curiosity is piqued!

Tracking Issue: Changelog approach

1

As we get more formal and disciplined about using the EIP lifecycle and iterating CAIPs in "Review" mode, we should add changelogs any time a substantial normative change is made...

update native urls secn in ipfs in the browser

1

# Describe your changes Renamed "Native URLs" to "IPFS-Scheme URLs" after discussion with some core folks in the filecoin slack earlier today. # Files changed docs/how-to/address-ipfs-on-web.md # What issue(s) does...

Discussed on today's call, we resolved that each Sidetree spec going forward should include for its specific chain or other substrate: - value-locking (~= "staking") params (anchor for tokenomics, slashing,...

revisiting @gobengo's discussion [here](https://github.com/orgs/ucan-wg/discussions/107#discussioncomment-7911638) might be worth folding into a general editorial rejiggering mentioned on today's call :D

Tracking Issue: Should idempotency (or not) of certain activities be explicit?

8

Great point [here](https://socialhub.activitypub.rocks/t/fep-c648-blocked-collection/3349/8) in a thread about something tangential. Want to make sure this is picked up later if a new major version of the spec is ever undertaken. In...

[Errata] CAIP-122 table to match normative changes in PR 236

1

hopefully closes #266 . thanks again to @jdsika for pointing it out and @glitch-txs for pointing out implementation issues in the field