hi friends! yesterday I attempted to run a node on a fresh amazon ec2 nano instance. I SCPed the lmdb data from another server, and started monerod. it took a couple hours to get back to synchronized state (since during SCP new blocks were added to the blockchain), but it worked! however, afterwards, it didn't stay in sync for long... snipboard.io/Sl1FZP.jpg Now I'm 6 hours

behind. I really thought after reaching synchronization it wouldn't be a burden on the instance to keep it up-to-date. Any ideas why it's happening? Thanks

(wrong channel to ask?)

It shouldn't be a burden. For starte i would check if you or your provider are blocking incoming connection. The question is more appropriate in #monero btw :)

yes it's blocked, I had no issue synchronizing while blocking incoming connections on other servers though

thank you I will try this now.

TL;DR: Cleaner device architecture will allow the hardware wallet vendors to integrate with Monero, without needing to merge their implementations into MoneroCore.

If somebody wants to discuss this, I will read it later. I need a nap.

I'm out of my depth. Does monero use ECDSA or EdDSA signing curves?

looking at this: docs.curv.co/advanced-flow/ecdsa-black-box-signing

effectively a way to add support for monero to Curv on my own

rupee[m]1: ecdsa and eddsa are signature algorithms, where eddsa is designed to go with the ed25519 elliptic curve; monero used ed25519 but a different signature algorithm called CLSAG

uses*

thank you. so probably not possible with this service

luigi1111w: merges today? :D

.merges

I think #7358 is ready now

mer-ges! mer-ges!

merge merge merge