Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

error from node construction: expected ed25519 data size to be 64 or 96, got 32

See original GitHub issue

👉️ Please describe what you were doing when this error happened.

Specifications

OS: win32
IPFS Desktop Version: 0.20.5
Electron Version: 18.0.3
Chrome Version: 100.0.4896.75

Error

Error: Initializing daemon...
go-ipfs version: 0.12.2
Repo version: 12
System version: amd64/windows
Golang version: go1.16.15
2022-05-09T21:43:29.353-0300	ERROR	cmd/ipfs	ipfs/daemon.go:430	error from node construction: expected ed25519 data size to be 64 or 96, got 32

Error: expected ed25519 data size to be 64 or 96, got 32

    at errorTemplate (C:\Users\Windows\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\daemon\migration-prompt.js:78:49)
    at Object.loadWindow (C:\Users\Windows\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\daemon\migration-prompt.js:115:26)
    at startIpfsWithLogs (C:\Users\Windows\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\daemon\daemon.js:163:25)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async module.exports (C:\Users\Windows\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\daemon\daemon.js:205:15)
    at async startIpfs (C:\Users\Windows\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\daemon\index.js:46:17)
    at async module.exports (C:\Users\Windows\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\