HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
glassroom
sata_attention
Python2026–2026
glassroom / sata_attention

sata_attention

Reference implementation of "Self-Attention at Constant Cost per Token via Symmetry-Aware Taylor Approximation" (Heinsen and Kozachkov, 2026)

3Distinct people
4Mentions
0Explicit recommenders
36GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Reference implementation of "Self-Attention at Constant Cost per Token via Symmetry-Aware Taylor Approximation" (Heinsen and Kozachkov, 2026)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval4 dated mentions

Observed mentions: 2026-02-04 15:20:21 UTC to 2026-02-07 15:20:26 UTC.

0122026-02-04 15:00:00 UTC to 2026-02-04 18:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsFeb 4, 15:002026-02-04 18:00:00 UTC to 2026-02-04 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-02-04 21:00:00 UTC to 2026-02-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-05 00:00:00 UTC to 2026-02-05 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-05 03:00:00 UTC to 2026-02-05 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-05 06:00:00 UTC to 2026-02-05 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-05 09:00:00 UTC to 2026-02-05 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-05 12:00:00 UTC to 2026-02-05 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-05 15:00:00 UTC to 2026-02-05 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-05 18:00:00 UTC to 2026-02-05 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-05 21:00:00 UTC to 2026-02-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-06 00:00:00 UTC to 2026-02-06 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-06 03:00:00 UTC to 2026-02-06 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 6, 03:002026-02-06 06:00:00 UTC to 2026-02-06 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-06 09:00:00 UTC to 2026-02-06 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-06 12:00:00 UTC to 2026-02-06 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-06 15:00:00 UTC to 2026-02-06 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-06 18:00:00 UTC to 2026-02-06 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-06 21:00:00 UTC to 2026-02-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-07 00:00:00 UTC to 2026-02-07 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-07 03:00:00 UTC to 2026-02-07 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-07 06:00:00 UTC to 2026-02-07 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-07 09:00:00 UTC to 2026-02-07 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-07 12:00:00 UTC to 2026-02-07 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-07 15:00:00 UTC to 2026-02-07 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 7, 15:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 4, 15:002026-02-04 15:00:00 UTC2026-02-04 18:00:00 UTC202
Feb 4, 18:002026-02-04 18:00:00 UTC2026-02-04 21:00:00 UTC101
Feb 4, 21:002026-02-04 21:00:00 UTC2026-02-05 00:00:00 UTC000
Feb 5, 00:002026-02-05 00:00:00 UTC2026-02-05 03:00:00 UTC000
Feb 5, 03:002026-02-05 03:00:00 UTC2026-02-05 06:00:00 UTC000
Feb 5, 06:002026-02-05 06:00:00 UTC2026-02-05 09:00:00 UTC000
Feb 5, 09:002026-02-05 09:00:00 UTC2026-02-05 12:00:00 UTC000
Feb 5, 12:002026-02-05 12:00:00 UTC2026-02-05 15:00:00 UTC000
Feb 5, 15:002026-02-05 15:00:00 UTC2026-02-05 18:00:00 UTC000
Feb 5, 18:002026-02-05 18:00:00 UTC2026-02-05 21:00:00 UTC000
Feb 5, 21:002026-02-05 21:00:00 UTC2026-02-06 00:00:00 UTC000
Feb 6, 00:002026-02-06 00:00:00 UTC2026-02-06 03:00:00 UTC000
Feb 6, 03:002026-02-06 03:00:00 UTC2026-02-06 06:00:00 UTC000
Feb 6, 06:002026-02-06 06:00:00 UTC2026-02-06 09:00:00 UTC000
Feb 6, 09:002026-02-06 09:00:00 UTC2026-02-06 12:00:00 UTC000
Feb 6, 12:002026-02-06 12:00:00 UTC2026-02-06 15:00:00 UTC000
Feb 6, 15:002026-02-06 15:00:00 UTC2026-02-06 18:00:00 UTC000
Feb 6, 18:002026-02-06 18:00:00 UTC2026-02-06 21:00:00 UTC000
Feb 6, 21:002026-02-06 21:00:00 UTC2026-02-07 00:00:00 UTC000
Feb 7, 00:002026-02-07 00:00:00 UTC2026-02-07 03:00:00 UTC000
Feb 7, 03:002026-02-07 03:00:00 UTC2026-02-07 06:00:00 UTC000
Feb 7, 06:002026-02-07 06:00:00 UTC2026-02-07 09:00:00 UTC000
Feb 7, 09:002026-02-07 09:00:00 UTC2026-02-07 12:00:00 UTC000
Feb 7, 12:002026-02-07 12:00:00 UTC2026-02-07 15:00:00 UTC000
Feb 7, 15:002026-02-07 15:00:00 UTC2026-02-07 18:00:00 UTC101

What Hacker News says

4 sources
The github repository's first toy example is with 8 Taylor terms, applied to a context with 1B tokens, each token with 1K heads: https://github.com/glassroom/sata_attention That toy example is not practical with the quadratic formulation, because it would require computing and storing 1K attention matrices, each with 1B×1B dot-product scores. For example, at Float32 precision, those attention matrices would consume approximately 1K x 1B x 1B x 4 bytes = 3,725,290,298.5 Terabytes of memory, which is not practical. Like every other proposed method, this one must be tested too. If it performs well in practice, AI service providers who ignore it will find themselves at a disadvantage. Otherwise, the mathematical techniques introduced by this work are likely useful for other applications besides Transformer attention.
In Attention at Constant Cost per Token via Symmetry-Aware Taylor Approximation

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.