Skip to content

Instantly share code, notes, and snippets.

View geoff-m's full-sized avatar

Geoff McQueen geoff-m

View GitHub Profile
@georgemitenkov
georgemitenkov / byte-types-or-how-to-get-rid-of-i8-abuse-for-chars-in-llvm-ir.md
Last active June 8, 2024 08:58
Byte types, or how to get rid of i8 abuse for chars in LLVM IR

Byte types, or how to get rid of i8 abuse for chars in LLVM IR

Authors: George Mitenkov, Nuno Lopes, Juneyoung Lee

Date: 15.10.2021

Part 0, where we introduce our work

This May, together with Nuno Lopes and Juneyoung Lee we made a proposal to add a new

-- Note: example given is for SQLite but can be adapted to other SQL
-- This is a fast query to sample random rows
-- It gets a list of existing row identifiers (rowids),
-- materializes, sorts, and picks 10.
SELECT * FROM test
WHERE rowid IN
(SELECT rowid FROM test
ORDER BY random() LIMIT 10);
@gavinandresen
gavinandresen / TransactionFeeProposal.md
Created June 20, 2012 18:24
Transaction Fee rework proposal

Reworking Bitcoin Transaction Fees

Transaction fees as they are currently implemented in the original Bitcoin code suffer from a few problems:

  • The rules are complicated and ad-hoc
  • Fees are hard-coded and do not reflect real costs
  • Adding fees to a transaction doesn't necessarily make it more likely the transaction will be confirmed more quickly.

I'm proposing changing the rules miners use to decide what transactions to include in their blocks, and changing the way clients tell users whether or not any particular transaction "needs" a fee to be confirmed in a reasonable amount of time.