What works, if anything?

General
1

Given the strong presence of our hyper-active Council and Community in these public (i.e. not in a walled-off apps closed to the world) venues where potential users builders and (gasp!) buyers might see it, one can’t help but feel “The future is so bright I have to wear shades”!

Now I just miss one key piece of info before I start brainstorming what to build: what known-to-work, frustration-free examples of getting started with cMixx services exist today?

Background: last time I tried ( Do xxDK (and validator rules) need an update? ) I ended up wasting hours of my time without getting anything in return. Some “workarounds” were mentioned, but not elaborated on.

2

Did some fixes for htmljs example here

It will now show network status
and uses local wasm_exec.js since https://elixxir-bins.s3-us-west-1.amazonaws.com/wasm/xxdk-wasm-0.3.19/dist/wasm_exec.js gives CORS error.

Screenshot 2025-10-25 at 10.36.30 AM
Screenshot 2025-10-25 at 10.36.30 AM2028×1454 144 KB

Screenshot 2025-10-25 at 10.21.21 AM
Screenshot 2025-10-25 at 10.21.21 AM3694×1530 465 KB

Updated commands (for fetching wasm_exec.js locally before dev server)

mkdir -p dist
curl -o dist/wasm_exec.js \
  https://elixxir-bins.s3-us-west-1.amazonaws.com/wasm/xxdk-wasm-0.3.19/dist/wasm_exec.js
python3 -m http.server

It takes some time for network to be ready, I suppose due local ndf file not updated and therefore it takes time to prepare working set of network.

2 Likes
3

Continuing from xxB-2024-003: Haven Browser Extension Implementation - #16 by m.f since it’s more appropriate to ask in this topic: I’ve never understood (since the first xxDK) why demos cannot load a Haven identity file and join a channel.

How is this Related to the browser extension? Well, I haven’t used it but I’ve seen a video demo and was thinking it might be possible to:

a) Have an ID store (could be independent from Haven cache)

b) Then, if an API is exposed, one could auth to the extension which would handle “load & login”. Maybe there’s a version of that already, but in the video a new Haven identity was created so I don’t know.

c) Similarly to Web wallets, one could even store a dict of identities and channels, to have everything in one place. Then, finally, apps like this simpler chat app (not necessarily Haven) could use the extension as a kind of Web wallet, where Haven identity is like wallet address, and channels are like fungible assets… In cases like this, convenience is required, so the ability to load 1 identity and 1 channel would be sufficient. Load, message, unload.

With this approach it would be possible to use cMixx for comms and notification from apps (automation) which is a big pain point with Haven.