ed25519 | Optimized version of the reference implementation of Ed25519

I want to sign a JWS (json web signature) with a private key generated through Ed25519 on a clients device. Then send this signature to my backend and verify it with the public key. To get familiar with the procedure I want to try to sign and verify a JWS in node js.
Both my private and public key are already generated and are available in base58. This is my current attempt at signing a JWT with an Ed25519 privateKey:

I'm stucked trying to launch a Github actions workflow. The Flutter project has a dependency of a custom package. I have this custom package in a Github repository. This is the way I set up this dependency in the pubspec.yaml:

When querying archival node for transactions with EXPERIMENTAL_tx_status method, some transactions have no receipts while having receipts_outcome. How is that possible, and how is that transaction different from others?

If I understand correctly, receipts_outcome are the results of applying receipts. According to explorer, this transaction has Convert Transaction To Receipt part, so there should be some receipts generated.

According to documentation

A Receipt is the only actionable object in the system. When we talk about "processing a transaction" on the NEAR platform, this eventually means "applying receipts" at some point.

A good mental model is to think of a Receipt as a paid message to be executed at the destination (receiver). And a Transaction is an externally issued request to create the Receipt (there is a 1 to 1 relationship).

My query

I have cloned this NEAR REST API SERVER repo into my local system and haven't made any changes to its original code. Only added console logs for debugging purpose. Using its API, I have successfully deployed a contract to testnet account and also called that contract.

But when comes to NFT part, its not working. I'm calling /mint_nft API and getting 500 Internal Server Error.

It's breaking here:

let create_token = await token.ViewNFT(tokenId, contract);

create_token is null.

If I do minting with NEAR CLI, its working fine and I can see that NFT in my testnet wallet..

near call $ID nft_mint '{"token_id": "02", "receiver_id": "'$ID'", "token_metadata": { "title": "Design #2", "description": "Art Design", "media": "https://ipfs.io/ipfs/Qme7ss3ARVgxv6rXqVPiikMJ8u2NLgmgszg13pYrDKEoiu", "copies": 1}}' --accountId $ID --deposit 0.1

I'm having some trouble installing the python cryptography package on my raspberry pi, specifically with python version 3.9.8 (installed with pyenv). The cryptography package is installed on my system using pacman (python-cryptography package), and thus works using the main python interpreter (3.10.1). However, I need some version of python 3.9 specifically for another package I am using in this project. Any time I try to install cryptography through the python 3.9.8 environment, I get the following error:

I have ec2 instance with ubuntu v20.04 and it has python v3.8.10 and pysftp 0.2.9.

I have generate .pem file from .ppk file using below command

puttygen sftp_server.ppk -O private-openssh -o sftp_server.pem

I am able to connect successfully to sftp server using command line-

I have a private key as a String and I want to convert it to PrivateKey

I tried a tutorial to set up GitHub SSH key, but when I type in the prompt it shows me the ed25519 instead of the rsa keyfingerprint.

Any pointer on how to add the rsa key fingerprint?

I have been unable to access servers via SSH after a recent upgrade to Windows 11.

I keep getting a permission denied (publickey) error.

I have tried regenerating new public keys with ed25519 instead of the deprecated rsa and I still get the same error.

I have seen answers alluding to file permissions but am afraid am not sure what files they are referring to.