Event signature verification

[0xtrr]

Hi! I'm working on a Blossom implementation and want to verify the signature on the authentication event. I was looking through the code in this library but I can't seem to figure out how I can verify the signature of an event?

[tcheeric]

It's not implemented, but I've found this guide explaining how the process works. https://bips.xyz/340#user-content-verification Can you confirm this is what you're looking for?  -- Sent with Tuta; enjoy secure & ad-free emails: https://tuta.com 1 May 2024, 16:27 by ***@***.***:

…

Hi! I'm working on a > Blossom <https://github.com/hzrd149/blossom/blob/master/README.md>> implementation and want to verify the signature on the > authentication event <https://github.com/hzrd149/blossom/blob/master/Server.md#authorization-events>> . I was looking through the code in this library but I can't seem to figure out how I can verify the signature of an event? — Reply to this email directly, > view it on GitHub <#157>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQMG7E3HATGT5COPMLDJGDZAECWLAVCNFSM6AAAAABHCEE55KVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI3TGNRZG44TMMQ>> . You are receiving this because you are subscribed to this thread.> Message ID: > <tcheeric/nostr-java/issues/157> @> github> .> com>

[0xtrr]

It's not implemented, but I've found this guide explaining how the process works. https://bips.xyz/340#user-content-verification Can you confirm this is what you're looking for?  -- Sent with Tuta; enjoy secure & ad-free emails: https://tuta.com 1 May 2024, 16:27 by @.***:
…
Hi! I'm working on a > Blossom https://github.com/hzrd149/blossom/blob/master/README.md> implementation and want to verify the signature on the > authentication event https://github.com/hzrd149/blossom/blob/master/Server.md#authorization-events> . I was looking through the code in this library but I can't seem to figure out how I can verify the signature of an event? — Reply to this email directly, > view it on GitHub <#157>> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/ABQMG7E3HATGT5COPMLDJGDZAECWLAVCNFSM6AAAAABHCEE55KVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI3TGNRZG44TMMQ> . You are receiving this because you are subscribed to this thread.> Message ID: > </issues/157> @> github> .> com>

Yeah that should be it

[tcheeric]

OK, noted. I'll work on it this week. It's a good feature to have indeed.  PS: Please note that current dev work is on the develop branch.

…

-- Sent with Tuta; enjoy secure & ad-free emails: https://tuta.com 1 May 2024, 17:20 by ***@***.***:

> > > It's not implemented, but I've found this guide explaining how the process works. >> https://bips.xyz/340#user-content-verification>> Can you confirm this is what you're looking for?  -- Sent with Tuta; enjoy secure & ad-free emails: >> https://tuta.com>> 1 May 2024, 16:27 by >> @>> .***: > >> … <> > Hi! I'm working on a > Blossom >> https://github.com/hzrd149/blossom/blob/master/README.md>> > implementation and want to verify the signature on the > authentication event >> https://github.com/hzrd149/blossom/blob/master/Server.md#authorization-events>> > . I was looking through the code in this library but I can't seem to figure out how I can verify the signature of an event? — Reply to this email directly, > view it on GitHub <>> #157 <#157>>> >> , or > unsubscribe >> https://github.com/notifications/unsubscribe-auth/ABQMG7E3HATGT5COPMLDJGDZAECWLAVCNFSM6AAAAABHCEE55KVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI3TGNRZG44TMMQ>> > . You are receiving this because you are subscribed to this thread.> Message ID: > <>> /issues/157 <#157>>> > @> github> .> com> > > > Yeah that should be it — Reply to this email directly, > view it on GitHub <#157 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQMG7DZV44RP3AGN6JN5BLZAEI33AVCNFSM6AAAAABHCEE55KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBYG4YDQOJWGA>> . You are receiving this because you commented.> Message ID: > <tcheeric/nostr-java/issues/157/2088708960> @> github> .> com>

[0xtrr]

OK, noted. I'll work on it this week. It's a good feature to have indeed.  PS: Please note that current dev work is on the develop branch.
…
-- Sent with Tuta; enjoy secure & ad-free emails: https://tuta.com 1 May 2024, 17:20 by @.***:

It's not implemented, but I've found this guide explaining how the process works. >> https://bips.xyz/340#user-content-verification>> Can you confirm this is what you're looking for?  -- Sent with Tuta; enjoy secure & ad-free emails: >> https://tuta.com>> 1 May 2024, 16:27 by >> @>> .***: > >> … <> > Hi! I'm working on a > Blossom >> https://github.com/hzrd149/blossom/blob/master/README.md>> > implementation and want to verify the signature on the > authentication event >> https://github.com/hzrd149/blossom/blob/master/Server.md#authorization-events>> > . I was looking through the code in this library but I can't seem to figure out how I can verify the signature of an event? — Reply to this email directly, > view it on GitHub <>> #157 <#157>>> >> , or > unsubscribe >> https://github.com/notifications/unsubscribe-auth/ABQMG7E3HATGT5COPMLDJGDZAECWLAVCNFSM6AAAAABHCEE55KVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI3TGNRZG44TMMQ>> > . You are receiving this because you are subscribed to this thread.> Message ID: > <>> /issues/157 <#157>>> > @> github> .> com> > > > Yeah that should be it — Reply to this email directly, > view it on GitHub <#157 (comment)>> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/ABQMG7DZV44RP3AGN6JN5BLZAEI33AVCNFSM6AAAAABHCEE55KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBYG4YDQOJWGA> . You are receiving this because you commented.> Message ID: > </issues/157/2088708960> @> github> .> com>

Awesome, thanks!

[tcheeric]

Actually, I was wrong.

The verification method exists already, it is in the Schnorr class in the crypto module, here.

I am adding a test routine for it now and will update the code accordingly.

[tcheeric]

It's now merged into the develop branch

Use the wrapper method Nostr.verify(GenericEvent) from the api module to verify the event's signature.

I hope this helps.

[0xtrr]

Thanks! I seem to have some problems referencing the develop build on Jitpack. Shouldn't I be able to reference the develop branch build like this:

                <dependency>
			<groupId>com.github.tcheeric</groupId>
			<artifactId>nostr-java</artifactId>
			<version>develop-SNAPSHOT</version>
		</dependency>

Maven says it can't find it. I've also enabled snapshot builds in the tag for jitpack:

                <repository>
			<id>jitpack.io</id>
			<url>https://jitpack.io</url>
			<snapshots>
				<enabled>true</enabled>
				<updatePolicy>always</updatePolicy>
			</snapshots>
		</repository>

[tcheeric]

I need to push a new release first. It will be done in the next couple of days. I'll let you know.  -- Sent with Tuta; enjoy secure & ad-free emails: https://tuta.com 2 May 2024, 17:47 by ***@***.***:

…

Thanks! I seem to have some problems referencing the develop build on Jitpack. Shouldn't I be able to reference the develop branch build like this: <dependency> <groupId>com.github.tcheeric</groupId> <artifactId>nostr-java</artifactId> <version>develop-SNAPSHOT</version> </dependency> Maven says it can't find it. I've also enabled snapshot builds in the tag for jitpack: <repository> <id>jitpack.io</id> <url>https://jitpack.io</url> <snapshots> <enabled>true</enabled> <updatePolicy>always</updatePolicy> </snapshots> </repository> — Reply to this email directly, > view it on GitHub <#157 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQMG7CU7QVOFCDITCJJR4LZAJUZJAVCNFSM6AAAAABHCEE55KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJRGA2DENBXGM>> . You are receiving this because you modified the open/close state.> Message ID: > <tcheeric/nostr-java/issues/157/2091042473> @> github> .> com>

[tcheeric]

I'll release later today, in the evening. Will let you know as soon as it's available. 

…

-- Sent with Tuta; enjoy secure & ad-free emails: https://tuta.com 2 May 2024, 17:47 by ***@***.***:

Thanks! I seem to have some problems referencing the develop build on Jitpack. Shouldn't I be able to reference the develop branch build like this: <dependency> <groupId>com.github.tcheeric</groupId> <artifactId>nostr-java</artifactId> <version>develop-SNAPSHOT</version> </dependency> Maven says it can't find it. I've also enabled snapshot builds in the tag for jitpack: <repository> <id>jitpack.io</id> <url>https://jitpack.io</url> <snapshots> <enabled>true</enabled> <updatePolicy>always</updatePolicy> </snapshots> </repository> — Reply to this email directly, > view it on GitHub <#157 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQMG7CU7QVOFCDITCJJR4LZAJUZJAVCNFSM6AAAAABHCEE55KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJRGA2DENBXGM>> . You are receiving this because you modified the open/close state.> Message ID: > <tcheeric/nostr-java/issues/157/2091042473> @> github> .> com>

[tcheeric]

New release is out. Let me know if you need any help or have questions.  -- Sent with Tuta; enjoy secure & ad-free emails: https://tuta.com 2 May 2024, 17:47 by ***@***.***:

…

Thanks! I seem to have some problems referencing the develop build on Jitpack. Shouldn't I be able to reference the develop branch build like this: <dependency> <groupId>com.github.tcheeric</groupId> <artifactId>nostr-java</artifactId> <version>develop-SNAPSHOT</version> </dependency> Maven says it can't find it. I've also enabled snapshot builds in the tag for jitpack: <repository> <id>jitpack.io</id> <url>https://jitpack.io</url> <snapshots> <enabled>true</enabled> <updatePolicy>always</updatePolicy> </snapshots> </repository> — Reply to this email directly, > view it on GitHub <#157 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQMG7CU7QVOFCDITCJJR4LZAJUZJAVCNFSM6AAAAABHCEE55KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJRGA2DENBXGM>> . You are receiving this because you modified the open/close state.> Message ID: > <tcheeric/nostr-java/issues/157/2091042473> @> github> .> com>