Skip to content
View remyers's full-sized avatar
⚡
⚡
64 followers · 27 following

Achievements

Achievement: Pair ExtraordinaireAchievement: QuickdrawAchievement: Pull Sharkx2Achievement: Arctic Code Vault ContributorAchievement: Starstruck
BetaSend feedback

Achievements

Achievement: Pair ExtraordinaireAchievement: QuickdrawAchievement: Pull Sharkx2Achievement: Arctic Code Vault ContributorAchievement: Starstruck
BetaSend feedback
Block or Report

Block or report remyers

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Pinned

  1. ACINQ/eclair ACINQ/eclair Public

    A scala implementation of the Lightning Network.

    Scala 1.2k 263

  2. bitcoin bitcoin Public

    Forked from bitcoinops/bitcoin

    Bitcoin Core integration/staging tree

    C++ 1

  3. yakshaver.org yakshaver.org Public

    Forked from bytabit/bytabit.github.io

    https://yakshaver.org

    3

  4. async-payments user story: donation ... async-payments user story: donation QR code
    1 
    The async-payment user story I'm interested in exploring is a mobile user (not always connected) who wants to receive donations (no PoP) via a static invoice from another mobile user.
    2 
    
              
    
              
    
                3
                
    My understanding of how this could work:
    
              
    
              
    
                4
                
    
              
    
              
    
                5
                
    1) The static invoice should contain a blinded route to the payment receiver via their LSP and an ephemeral public key that the payment sender will use to encrypt the last hop of a payment onion containing a keysend TLV. The LSP of the payment receiver must support store-and-forward of onion messages.
    
              
    
          
    
    
    
  
    

    5.