wireguard-vanity-address
bips
wireguard-vanity-address | bips | |
---|---|---|
5 | 1,283 | |
406 | 9,004 | |
- | 1.8% | |
0.0 | 6.8 | |
over 1 year ago | 7 days ago | |
Rust | Wikitext | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wireguard-vanity-address
-
Possible to define tunnel name in config file?
https://github.com/warner/wireguard-vanity-address (rust)
-
Dangerous toys: Anything to ed25519 (SSH Keys)
another dangerous toy I particularly enjoy, vanity keys:
https://github.com/warner/wireguard-vanity-address
Although not as dangerous since the entropy of the rng is (mostly?) still there. If I'm doing the handwaving right, it's base64 where each char contains 6 bits, so you reduce the effective keysize to 256-6*$num_chars -- cryptographers tell me how wrong I am :)
-
Wireguard | Pre-shared key | What's required?
The keys are generated in a mathematically related pair, so you can't just create one from scratch. There are tools that will generate lots of random keys and select for a predetermined string in them, like this: https://github.com/warner/wireguard-vanity-address
- wg-manage: Central management of Wireguard configs
- wireguard + resolved + networkd: vpn server, ipv4 forwarding
bips
-
Understanding and avoiding visually ambiguous characters in IDs
Modern bitcoin addresses use a base-32 character set that leaves out some of the most ambiguous pairs and also permutes the address ordering so that the most visually similar remaining characters produce single bit errors which are better handled by the addresses error detecting (and potentially correcting) code.
https://github.com/bitcoin/bips/blob/master/bip-0173.mediawi...
-
Bitcoin Block 840000
Context: Bitcoin miners have just adopted a 50% pay cut for themselves. This pay cut was baked into Bitcoin protocol at the launch of the network (mostly, see "BIP 42" [1]). The OP link gives information about the block in which this pay cut was made.
I get that HN comments tend to dismiss Bitcoin. But the fact that for the fourth time this pay cut has happened without a hitch speaks volumes to what makes Bitcoin interesting: It's a rare combination of economic incentives and technology that keeps chugging. Nobody can stop it. And it's extremely resistant to change. It requires no governmental approval. All attempts at subversion or interference have failed. There aren't many things that come close to that kind of record.
[1] https://github.com/bitcoin/bips/blob/master/bip-0042.mediawi...
-
Generating and Working With ScriptPubKeys in Bitcoin Transactions
Bitcoin transactions involve locking funds in scripts, which can only be spent if those locking conditions are met. The part of the script that expresses these locking conditions are called ScriptPubKeys. On the other hand, the part that provides unlocking scripts to satisfy the locking conditions is referred to as ScriptSig for legacy transactions, and ScriptWitness for SegWit Transactions. These scripts are evaluated by a stack-based language called Script. This article will mainly focus on ScriptPubKeys.
- Blue Wallet and seed phrases
-
Nano S seed compromised?
Here’s the reference https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki
-
Do you use 12 - 24 words?
There are 5 271 537 971 301 488 476 000 309 317 528 177 868 800 possible permutations of the bip39 wordlist found here: https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt when using 12 word seeds. You probably have better change to win the lottery every week for the rest of your life than cracking a 12 word seed in correct order
- 24 words
- Creating a custom Bip39 brain wallet
-
SEC Charges Kraken for Operating as an Unregistered Securities Exchange
No one controls Bitcoin, because it's a protocol. Bitcoin Core is the reference implementation, but there are others, and anyone can create new implementations if they wish. Also, the Bitcoin Core maintainers can't just change something on a whim, because users would then switch to another fork. Maintainers (or miners or other groups) can't force their changes on users, because everyone can decide on their own which version they want to use.
The protocol development happens through BIPs (Bitcoin improvement proposals): https://github.com/bitcoin/bips
BIPs are discussed for years, before (and if) they are implemented, and basically everyone needs to agree on them, because no one wants to fork the blockchain, which could be devastating.
-
Recover Cool Wallet seed to a Ledger?
All the seeds generated from the CoolWallet (Number / Word) adhere to the BIP-39 protocol.
What are some alternatives?
wg-friendly-peer-names - Provides a way to give wireguard peers a friendlier and more readable name
brainflayer - A proof-of-concept cracker for cryptocurrency brainwallets and other low entropy key algorithms.
wireguard-vanity-keygen - WireGuard vanity key generator
P2P-Trading-Exchanges - Person-to-Person bitcoin Trading Exchanges
wireguard-key-generator - A Linux Shell progrm that generates Public and Private Keys for your WireGuard Server and Client configuration files.
solidity - Solidity, the Smart Contract Programming Language
libsodium - A modern, portable, easy to use crypto library.
EIPs - The Ethereum Improvement Proposal repository
lokey - A tool that makes it easy to work with and convert between cryptographic key formats
bip39 - A web tool for converting BIP39 mnemonic codes
solana - Web-Scale Blockchain for fast, secure, scalable, decentralized apps and marketplaces.
btcrecover - An open source Bitcoin wallet password and seed recovery tool designed for the case where you already know most of your password/seed, but need assistance in trying different possible combinations.