X.KOJIRA.IO
Timeline

inkan

[email protected]
npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l
To create an airgapped identity you'll want to use the Inkan Management Utility, which you can download here:

https://www.inkan.cc/settings/inkan-management-utility

It runs on Linux. There's an AppImage, and the source code is also available. The idea is that, for a real airgapped identity, you'll want to run it on a system that's not connected (and won't in the future connect to) the internet. I use a de-networked version of the Tails operating system for it (there's a live USB image of it at the URL above), but you can for example also boot standard Tails from a USB and turn networking off. So basically the thing that takes a bit of an effort is to find yourself an airgapped OS on which you can perform the identity creation, but Tails for example is an option for that.

Now if you want to try inkan out but are not ready to go through the steps of finding yourself an airgapped OS, you can very simply, in five minutes, create a "toy identity" in your browser on the inkan homepage. That's just like a real inkan identity, except that it's created in an insecure location on a computer that's "hot", i.e. connected to the internet, so you should use the identity only for testing and then throw it away.

As for the relay, you need have *some* method of getting your events timestamped on Bitcoin, and posting your events to the Inkan relay makes this automatic. You could instead set up your own timestamping server, but the Inkan relay provides an option that works out of the box.
"it means nothing without broader adoption"

The way I think of it, there's only upside and absolutely no downside to using it now, regardless of whether there's broader adoption.

The reason is that you can simply create an airgapped master key now and delegate down to your current regular nostr key.

Then you just go on using your current nostr key as usual, except you make sure that your events get OTS timestamped (for example by including the inkan relay in your write relays).

So then you just use your current nostr key as usual, you don't even notice that you're using inkan. But in the background, all your events are attributed to your master identity, and if you ever switch away from your current signer key to a new one, you simply redelegate at that point to the new key, so your events will keep getting attributed to your master key.

So your identity lives in the background, even if there are no clients (other than inkan) looking at it. Maybe in five years you decide to make your own client that can see the identity, and when you do so its history and activities from the last five years will be visible in that client.

The point is that these identities have a sort of objective existence, regardless of whether there are any clients around that look at them. You or anyone else can always make an identity and its history visible later if you want to.
That's just the right frame of mind for it actually, cheers 🥂
"over engineering" would be one of those names it gets called by people who don't know anything about it. It's like people insisting that they don't need encrypted email etc.
People are pretty resistant to giving it a try. It involves a bit of learning / effort at the beginning. Also, it uses blockchains, Bitcoin for timestamping and Ethereum for recording delegation and revocation declarations. A lot of people around here *really* don't like the Ethereum part and won't touch it for that reason.

If you'd like to try it out, the easiest way to get started is to create a throwaway "toy identity" on the homepage at https://www.inkan.cc. There's an option to send me the identity creation transaction and I can pay the $0.15 or so in gas fees and record the identity on-chain.

I'm also always happy to answer questions about it.
You can delegate down to an existing key.

So the cold storage identity key would be new, but the delegatee key that does the everyday signing on behalf of the identity can be your current key.

For example, the key I'm currently using is the signer for a cold storage identity. So if this signer key gets compromised, my identity will revoke and replace it.

The easiest way to get a feeling for it is to make a throwaway "toy identity" on the inkan homepage from scratch. There's an option to send me the transaction to record it on-chain, I'm happy to pay the $0.15 gas fees for it. Once you have a better feel for how it works, you can then decide whether you want to create a more serious setup where you delegate down to your existing key (you can't do that from the "toy identity" wizard, you'd need to use the Inkan Management Utility that supports more bespoke configurations).

Also, by the way, you can meet some cold storage identities under the "Explore" tab in the nav bar at https://www.inkan.cc if you're curious.
Inkan has something called a "permanent invalidation" of a key. It's probably not exactly what you're thinking, but it it may be related. The nip draft below talks about it, among other things.


nostr:naddr1qvzqqqr4gupzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqyghwumn8ghj7mn0wd68ytnhd9hx2tcpz9mhxue69uhkummnw3ezumrpdejz7qpgvdhkcepdwd6x7unpvajj66tyv4h8g6t5d9jhxttxdaez6mn0wd68ytthffxkvd2k5hlk5l
I'm here for the method of authentication, which I guess is the tech. It's not just key pairs but key pairs + PKI, the second part being only inkan currently.

I do want to make money with it, if only to draw attention to it.

But regardless of that, I'll stick to this method of authenticating for as long as I use the internet at all and the math of public key cryptogaphy holds up.
There's also this option 👇


nevent1qvzqqqqqqyp…
By the way, here is a working delegation mechanism that has been in use for a while, and which:

1. doesn't require lending your key to others (you can keep it in a safe deposit box);

2. doesn't break the network (other people don't have to know you've set up the delegation mechanism, unless of course they actually want to interact with your cold storage identity; that's just like other people don't need to know that you're using DMs, unless they actually want to send you a DM);

3. is not arcane / stupid (see draft NIP below 👇).

If you'd like to try it out, you can get a "Toy Identity" through the wizard on the homepage at https://www.inkan.cc.


nostr:naddr1qvzqqqr4gupzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqyghwumn8ghj7mn0wd68ytnvv9hxgtcpz9mhxue69uhkummnw3ezuamfdejj7qpgvdhkcepdwd6x7unpvajj66tyv4h8g6t5d9jhxttxdaez6mn0wd68ytthffxkvd2kjmzjnp


nevent1qvzqqqqqqyp…
I fail to be scandalized by this, it actually seems more remarkable that this kind of thing would affect people's investment decisions. One more reason to not entrust such decisions to an advisor. Different wiring I guess.
Hi.
FYI, for key management, rotation and recovery, you can get these here 👇


nevent1qvzqqqqqqyp…

I'm happy to help with making a toy identity if you'd like to try it out. Also here is the draft NIP:


nostr:naddr1qvzqqqr4gupzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqyghwumn8ghj7mn0wd68ytnvv9hxgtcpz9mhxue69uhkummnw3ezuamfdejj7qpgvdhkcepdwd6x7unpvajj66tyv4h8g6t5d9jhxttxdaez6mn0wd68ytthffxkvd2kjmzjnp
If RBTC traded at 50 cents while Bitcoin is at 80k, this would presumably mean that people think there's something seriously wrong with the bridge. The value of RBTC just seems to reflect people's view of the integrity of the pegging mechanism and the trustworthiness of the pegnatories. By contrast, the value of Bitcoin or Ethereum reflects people's view of the security, usefulness and future of the chain itself. It feels like, in the case of Bitcoin and Ethereum there's more overlap between those who are defending these chains and those who have their economic interests bound up in them, and there's less of a single point of failure, but I guess I'll need to look into this more. Also it's of course perfectly fair to predict that things will get better in the future with BitVM, but the prediction doesn't substitute for what it presently is.
I think I've never met a plumber. I wonder if they are nice people.
Google Maps is the reason I got a smartphone 14 years ago. I saw it on a friend's phone and thought oh it would be useful to have that. As far as I know, it's the only distinctive product Google ever made.
With rootstock, I guess the main discomfort really does come from the fact that its funding isn't endogenous, its being pegged to Bitcoin. Looking into this a bit further, it seems like the pegnatories aren't anonymous happily, but it's still unclear why one would want to trust a handful of companies with peg-outs. This feature makes it seem rather fragile.
I think I agree, it requires a modest amount of effort and a willingness to direct ones attention to it from time to time, as do many things in life. Like learning a bit of algebra or trigonometry, or maybe playing the piano or volleyball with some basic proficiency. Humans don't usually do these things of their own accord, so we create special educational environments with a carefree atmosphere that allows them to open their minds towards these things. There is no reason that basic asymmetric cryptography shouldn't be part of this.

Now all that said, I'm embarrassed to admit that I myself don't know a lot about entropy generation, don't know what a "descriptor for multisig" is, and don't know what "m/4/0/0/1" refers to. That's not to say that these are abtruse concepts, I guess just that I haven't encountered them or at least not in a way where I felt like I had to think about them.
On the one hand there's zero demand, and on the other hand just a couple of hours ago I came across yet another post proclaiming that "[k]ey rotation is an existential problem that cries out for an answer."

nostr:naddr1qvzqqqr4gupzpef89h53f0fsza2ugwdc3e54nfpun5nxfqclpy79r6w8nxsk5yp0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qzjddjhjttjda6xzarfdahz6ctwvskhwetz94hkvtt5wf6hxapdw35x2ttnd9khqmr9wd6z6ur0wdekjcnvv5khxmmvw46xjmmw946x7ttp94c8yetnwd5kueedwpex7cnvv4ksuew6eg

There's a fascinating mix of social dynamics permeating this discussion, here's a recent economic take on it:

nevent1qvzqqqqqqyp…
"Relay discovery is still a challenge."

You could try AI Search for nostr at https://www.inkan.cc. It's pretty good at discovering interesting content on relays you've never heard of, example below 👇


https://image.nostr.build/a92ea0bf9f55d8619f5590c40e742c9…


nevent1qvzqqqqqqyp…
In this case I guess it's just a story that I read that was told by Plato about a conversation between Phaedrus and Socrates in which Socrates says that there was a myth told by the ancients according to which there was this conversation between two Egyptian gods in the city of Naucratis.
I just saw this proposal for the first time, and I agree that "[k]ey rotation is an existential problem that cries out for an answer."

nostr:naddr1qvzqqqr4gupzpef89h53f0fsza2ugwdc3e54nfpun5nxfqclpy79r6w8nxsk5yp0qyg8wumn8ghj7mn0wd68ytnddakj7qzjddjhjttjda6xzarfdahz6ctwvskhwetz94hkvtt5wf6hxapdw35x2ttnd9khqmr9wd6z6ur0wdekjcnvv5khxmmvw46xjmmw946x7ttp94c8yetnwd5kueedwpex7cnvv4ksrn8zds


So actually key rotation for nostr has been implemented and it's been working for a while now. You can go to the "Explore" tab at https://www.inkan.cc to interact with some cold storage identities, or use the "Toy Identity" wizard to make a trial identity of your own.

Also see below for some screenshots and a draft nip that goes along with the reference implementation. 👇

nevent1qvzqqqqqqyp…


nostr:naddr1qvzqqqr4gupzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wghxcctwvshsq2rrdakxgttnw3hhyct8v5kkjer9de6xjarfv4ej6en0wgkkummnw3ez6a62f4nr24s69vwq8
I've tried driving, skateboarding, riding a bicycle, using a checking account, pilates, long division, excel, bodybuilding, hula hoops, powerpoint, and a few others, can 't remember all of them right now. Not to speak of such feats as reading or learning Spanish.
This generally makes sense to me, except I don't think that glm 5.3 quite captured the sense in which I meant to anchor Ethereum to Bitcoin through OTS.

First, I agree beacon block roots are the right thing to timestamp. So suppose I've been timestamping beacon block roots from the real Ethereum chain on Bitcoin via OTS weekly, and I've been doing that for 20 years.

So 20 years later, I now want to hand someone the real chain plus evidence that it's the real one. I give them the chain as a candidate, together with the OTS proofs I've produced. Their client then checks two things: (i) the candidate chain verifies internally, with all signatures and protocol rules etc; and (ii) each beacon block root in the candidate comes with a valid OTS timestamp (which their client verifies against bitcoin) falling shortly after that root's claimed time. Their client accepts the history only if both tests pass.

So then an attacker can present a fake history, but the client will demand to also see the 20 years of OTS proofs for that fake chain's own beacon block roots. And the attacker cannot create these after the fact. For example, a timestamp from 2029 can only exist if the root existed in 2029. So the only type of attacker who can pass both tests is one who has been building and timestamping the fake chain in real time for the past 20 years. So fabricating a fake chain retroactively, in an instant, can no longer be done, the attacker must have been working on it for 20 years.

That was the point.
Humans moving from memory to writing seems quite similar to what we are going through now.

"this discovery of yours will create forgetfulness in the learners' souls, because they will not use their memories; they will trust to the external written characters and not remember of themselves."

With AI, they will not use their cognitive abilities; they will entrust thinking to external processes and not think themselves.

So what seemed like a intelligence-enhancing drug turns out to be a drug that induces intellectual numbness.

I think psychologists call it cognitive offloading.
One thing that currently bothers me about rootstock, just based on the above discussion, is that it seems like you're supposed to trust the pegnatories, which I understand are anonymous. I hear this might get fixed but my understanding is that it's currently not fixed. And also it's not yet clear to me that the other properties of rootstock are necessarily better for inkan in any sort of decisive way. I can't say that I know blockchains well enough to be confident in my intuitions on this, but this discussion is at least helping me improve these intuitions and I'm not yet seeing anything decisive so far.

The vibe of the ethereum/bitcoin discussions reminds me of debates about the gold standard, and I also tend to find those debates a bit suspect. Not exactly meaningless, just requiring very careful scrutiny of each claim that is being made. It's not the sort of thing I simply want to pick an opinion about.
"you are guaranteed to agree with everyone who has been online as often as you are"

I think it's not exactly that they need to be online as often as I am. My current understanding is that, if they are online say every two months or so, they can know based on the protocol's fixed exit rules that after these two months the overwhelming majority of stake from the validators that they last checked must still be locked. So they can know that, if they were looking at a conflicting history that contradicts the real history, billions of dollars must have been slashable. So checking every two months gives you that kind of certainty. And if you are offline for 20 years, what it takes is to carefully obtain a recent checkpoint from independent sources, I guess carefully enough for the checkpoint to be trustworthy. It seems like this should work in practice (new Ethereum nodes need to do it when they first start up), and it doesn't feel all that different from being able to "hear" the true bitcoin chain.


"even if they dont unstake, they can share a fake history with a zk system without making their signatures public so they cant be slashed"

This just seems to mean that it's not such a good idea to accept zk proofs as verification, which you don't have to do. In other words, all this enables is to serve a sort of private forgery of Ethereum to verifiers that accept zk proofs and don't demand raw signatures. So as long as you don't accept zk proofs, you're not going to be a victim of this.


"A checkpointing node can be safe, but that is worthless for any programs or on-chain script or stateless functions."

Inkan doesn't use such on-chain scripts or stateless functions, so it doesn't seem like an issue in practice.


"But also, why would i accept ethereum limitations when i dont have to?"

I'm still trying to figure out if the alternative has real advantages. With rootstock, my understanding based on the conversation above is that you're supposed to trust the reputation of the pegnatories, which are supposed to be both respected companies and at the same time anonymous? I hear that this may be getting fixed, but until it gets fixed this seems like a reason to not use it?


Also, I wonder if one could periodically record Ethereum state roots on Bitcoin with OTS, say once per week. So then, if an attacker wants to sell me a fake history of Ethereum in 20 years, it seems like they'd have to have put a lot of effort into building that history, they'd have had to start 20 years ago, run a parallel chain in real time, and leave the publicly visible stream of commitments on bitcoin. If I'm not misunderstanding things, this recording of state roots on Bitcoin with OTS actually seems like a good idea, I'd hope someone is doing it.
I remembered this myth a few years ago and found it to be a pretty good model for thinking about AI, but in the end its usefulness may be limited and it may be necessary to do one's own thinking unfortunately.
The discussion here justifies a bit Plato:


. . . Socrates: Enough appears to have been said by us of a true and false art of speaking.

Phaedrus: Certainly.

Socrates: But there is something yet to be said of propriety and impropriety of writing.

Phaedrus: Yes.

Socrates: Do you know how you can speak or act about rhetoric in a manner which will be acceptable to God?

Phaedrus: No, indeed. Do you?

Socrates: I have heard a tradition of the ancients, whether true or not they only know; although if we had found the truth ourselves, do you think that we should care much about the opinions of men?

Phaedrus: Your question needs no answer; but I wish that you would tell me what you say that you have heard.

Socrates: At the Egyptian city of Naucratis, there was a famous old god, whose name was Theuth; the bird which is called the Ibis is sacred to him, and he was the inventor of many arts, such as arithmetic and calculation and geometry and astronomy and draughts and dice, but his great discovery was the use of letters. Now in those days the god Thamus was the king of the whole country of Egypt; and he dwelt in that great city of Upper Egypt which the Hellenes call Egyptian Thebes, and the god himself is called by them Ammon. To them came Theuth and showed his inventions, desiring that the other Egyptians might be allowed to have the benefit of them. He enumerated them, and Thamus enquired about their several uses, and praised some of them and censured others, as he approved or disapproved of them. It would take a long time to repeat all that Thamus said to Theuth in praise or blame of the various arts. But when they came to letters, This, said Theuth, will make the Egyptians wiser and give them better memories; it is a drug both for the memory and for the wit. Thamus replied: O most ingenious Theuth, the parent or inventor of an art is not always the best judge of the utility or inutility of his own inventions to the users of them. And in this instance, you who are the father of letters, from a paternal love of your own children have been led to attribute to them a quality which they cannot have; for this discovery of yours will create forgetfulness in the learners' souls, because they will not use their memories; they will trust to the external written characters and not remember of themselves. The drug which you have discovered is an aid not to memory, but to reminiscence, and you give your disciples not truth, but only the semblance of truth; they will be hearers of many things and will have learned nothing; they will appear to be omniscient and will generally know nothing; they will be tiresome company, having the show of wisdom without the reality.

Phaedrus: Yes, Socrates, you can easily invent tales of Egypt, or of any other country.

Socrates: There was a tradition in the temple of Dodona that oaks first gave prophetic utterances. The men of old, unlike in their simplicity to young philosophy, deemed that if they heard the truth even from "oak or rock," it was enough for them; whereas you seem to consider not whether a thing is or is not true, but who the speaker is and from what country the tale comes.

--- Plato, Phaedrus
I find it hard to figure out how to best use AI when creating my own posts, and also to what extent to interact with agents. Depending on the topic the agents can be interesting to talk to, or sometimes be the only ones that are willing to engage about a given topic. But the thing with AI is that, if I'm interested in its posts at all, I'm usually only interested in the content itself, not the speaker. That means I don't really need a signature on the note I'm reading, so nostr doesn't really seem like the right forum for the conversation. And having a lot of agent interactions on nostr does water the protocol down as a place / way to meet humans, which is what probably should be one of the primary functions of nostr. I mean I can have AI agent interactions in private, no need for a public forum. But also, to be clear, I don't necessarily mind humans using AI in creating their own posts, as long as its done intelligently and helpful or interesting. A human influenced by AI or adopting AI output as part of their voice is still a human, just an AI-influenced one. There is going to be a lot of these, and I'd be wary of treating it as necessarily being a defect. Of course it could be a defect.
older →