Praveen Perera praveenperera

## kvac_rate_limiting.md

      
              1 file
            
          
              0 forks
            
          
                6 comments
              
            
              2 stars
            
          
                nothingmuch
                / kvac_rate_limiting.md
            
            
              Last active
              October 24, 2025 01:27
            
              
                reusable KVAC based rate limiting tokens with O(1) server storage
              
          
    Introduction

A blind signature based rate limiting tokens, or their keyed verification analogues (e.g. privacy pass) can be used to rate limit requests, but presents challenges with regards to stockpiling and interaction requirements (credential requests can be batched and done ahead of time subject to anti-stockpiling mitigations, but are still fundamentall O(N)).
The somewhat obvious idea (probably not novel, but I couldn't find a description) presented here uses the unlinkable multi-show property of anonymous credentials to construct token bucket filters with a one time setup, permitting non-interactive self-issuance of usage tokens whose honest usage is anonymous (tokens of a single credential or different credentials are indistinguishable).
One time set up

A client wishes to make repeated anonymous requests to a rate limited server.

  
## taproot.rs
// Bitcoin Dev Kit
// Written in 2021 by Alekos Filini <alekos.filini@gmail.com>
//
// Copyright (c) 2020-2021 Bitcoin Dev Kit Developers
//
// This file is licensed under the Apache License, Version 2.0 <LICENSE-APACHE
// or http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your option.
// You may not use this file except in accordance with one or both of these
// licenses.

## Flexible Dockerized Phoenix Deployments.md

      
              1 file
            
          
              43 forks
            
          
                15 comments
              
            
              210 stars
            
          
                jswny
                / Flexible Dockerized Phoenix Deployments.md
            
            
              Last active
              September 5, 2025 05:27
            
              
                A guide to building and running zero-dependency Phoenix (Elixir) deployments with Docker. Works with Phoenix 1.2 and 1.3.
              
          
    Prelude

I. Preface and Motivation

This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.
For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai
	// Bitcoin Dev Kit
	// Written in 2021 by Alekos Filini <alekos.filini@gmail.com>
	//
	// Copyright (c) 2020-2021 Bitcoin Dev Kit Developers
	//
	// This file is licensed under the Apache License, Version 2.0 <LICENSE-APACHE
	// or http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
	// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your option.
	// You may not use this file except in accordance with one or both of these
	// licenses.