- chat5 - application for unifying your chats
- Allows users to store messages from different chat platforms in dwn protocol
- Authenticates with did and accesses local
/chat
protocol to access all platforms available - Can encrypt messages at any level of the tree, etc.
- Platforms get listed under the
/chat
protocol path like so - Telegram:
/chat/telegram/{...}
- Discord:
/chat/discord/{...}
- Slack:
/chat/slack/{...}
- Signal:
/chat/signal/{...}
- 5ocial - same idea as chat but for social media; unifying your social media profiles
import { base64url } from '@scure/base'; | |
import { entropyToMnemonic } from '@scure/bip39'; | |
import { wordlist } from '@scure/bip39/wordlists/english'; | |
// Function to convert Base64URL string to Uint8Array | |
function base64UrlToUint8Array(b64url: string): Uint8Array { | |
return base64url.decode(b64url + '='.repeat((4 - (b64url.length % 4)) % 4)); | |
} | |
// Function to convert the private key to a BIP39 mnemonic |
import { Web5 } from '@web5/api'; | |
import { DidJwk, DidDht, BearerDid } from '@web5/dids'; | |
import { DwnRegistrar } from '@web5/agent'; | |
import { Web5UserAgent } from '@web5/user-agent'; | |
let initialize; | |
const instances = {}; | |
const storage = { | |
get: (key, _default) => { |
- In a clean folder, copy connect.ts and recover.ts
- Set a password in connect.ts
- Run
tsx connect.ts
and let it run. It'll hang at the sync, let it sit for a 10 sec or so then kill it. - Copy the recovery phrase that prints out, and make note of the did identities it created.
- Delete the
DATA
folder, paste the recovery phrase intorecover.ts
and runtsx recover.ts
Note
You'll need to checkout this branch on our repo and build locally: https://github.com/FormFree/web5-js/tree/api/web5-recover
Then you'll need to start a new npm project and run npm install /path/to/FormFree/web5-js/clone/api/web5-recover/branch
Welcome to the first ever DIDdevs meetup! Topics for this evening include:
Atlanta BitDevs is a place for free and open Bitcoin education in Atlanta. Discussions will be technical but are open to people of all skill levels. 📙 Atlanta BitDevs' reading groups are small sessions where we focus on a specific topic within Bitcoin development and help each other understand it through discussion.
- Website: https://atlantabitdevs.org/
- Discord: https://discord.com/invite/gQmJwWC5Ts
- Meetup Group: https://www.meetup.com/atlantabitdevs/
https://atlantabitdevs.org/2023/05/30/bitcoin-socratic-seminar-18/ https://www.meetup.com/atlantabitdevs/events/293790513/
- P2P and network changes
- Txns with min size of 65 bytes of non-witness data are now allowed by mempool and relay policy
- Continues to mitigate
CVE-2017-12842
64 byte vulnerability while opening up additional smaller transaction size use-cases
CVE-2017-18350
is a buffer overflow vulnerability which allows a malicious SOCKS proxy server to overwrite the program stack on systems with a signedchar
type (including common 32-bit and 64-bit x86 PCs).
https://atlantabitdevs.org/2023/04/18/bitcoin-socratic-seminar-17/ https://www.meetup.com/atlantabitdevs/events/292584775/
-
Why Stratum v2?
- Stratum v1 is old and has many problems
-
What is the Stratum protcol?
OP_VAULT
makes use of a highly secure key as an unlikely recovery path in the event of an unplanned unvaulting attempt by a bad actor
- Alice spends UTXOs into vault
- Alice is running software to monitor the blockchain for spends of the vault outpoints
- An unvaulting attempt is triggered: either by Alice or by Bob
- P2TR txs taking off!
- https://twitter.com/murchandamus/status/1624834282534449153
- Almost no one was using P2TR before ordinals
- context: TR = taproot
- TR was the softfork added to bitcoin ~2 years ago
- it was deemed so important and such an obvious win for bitcoin that it took precedence over other BIPs