libanubis-solver 2.0.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (135) hide show
  1. libanubis_solver-2.0.2/ATTRIBUTION.md +124 -0
  2. libanubis_solver-2.0.2/LICENSE +168 -0
  3. libanubis_solver-2.0.2/MANIFEST.in +8 -0
  4. libanubis_solver-2.0.2/Makefile +487 -0
  5. libanubis_solver-2.0.2/PKG-INFO +873 -0
  6. libanubis_solver-2.0.2/README.md +844 -0
  7. libanubis_solver-2.0.2/THIRD_PARTY_NOTICES.md +150 -0
  8. libanubis_solver-2.0.2/_anubis_solver_native/__init__.py +0 -0
  9. libanubis_solver-2.0.2/anubis_solver.py +1373 -0
  10. libanubis_solver-2.0.2/include/anubis-solver.h +267 -0
  11. libanubis_solver-2.0.2/libanubis_solver.egg-info/PKG-INFO +873 -0
  12. libanubis_solver-2.0.2/libanubis_solver.egg-info/SOURCES.txt +133 -0
  13. libanubis_solver-2.0.2/libanubis_solver.egg-info/dependency_links.txt +1 -0
  14. libanubis_solver-2.0.2/libanubis_solver.egg-info/entry_points.txt +2 -0
  15. libanubis_solver-2.0.2/libanubis_solver.egg-info/not-zip-safe +1 -0
  16. libanubis_solver-2.0.2/libanubis_solver.egg-info/requires.txt +4 -0
  17. libanubis_solver-2.0.2/libanubis_solver.egg-info/top_level.txt +2 -0
  18. libanubis_solver-2.0.2/pyproject.toml +53 -0
  19. libanubis_solver-2.0.2/setup.cfg +4 -0
  20. libanubis_solver-2.0.2/setup.py +93 -0
  21. libanubis_solver-2.0.2/src/api/anubis_api.c +1550 -0
  22. libanubis_solver-2.0.2/src/core/anubis_solver.c +3564 -0
  23. libanubis_solver-2.0.2/src/core/direct_run.c +138 -0
  24. libanubis_solver-2.0.2/src/core/kaggle_tensor_v/README.md +24 -0
  25. libanubis_solver-2.0.2/src/core/kaggle_tensor_v/run.py +143 -0
  26. libanubis_solver-2.0.2/src/core/nvidia_boost.c +295 -0
  27. libanubis_solver-2.0.2/src/cpu/avx2.s +584 -0
  28. libanubis_solver-2.0.2/src/cpu/avx512.s +780 -0
  29. libanubis_solver-2.0.2/src/cpu/neon.s +103 -0
  30. libanubis_solver-2.0.2/src/cpu/shani.s +178 -0
  31. libanubis_solver-2.0.2/src/fetch/anubis_fetch.c +1059 -0
  32. libanubis_solver-2.0.2/src/fetch/anubis_fetch.h +110 -0
  33. libanubis_solver-2.0.2/src/fetch/fetch_impersonate.c +594 -0
  34. libanubis_solver-2.0.2/src/fetch/fetch_impersonate.h +88 -0
  35. libanubis_solver-2.0.2/src/google/tpu/README.md +220 -0
  36. libanubis_solver-2.0.2/src/google/tpu/argon2_pjrt.c +2652 -0
  37. libanubis_solver-2.0.2/src/google/tpu/hashx_pjrt.c +1348 -0
  38. libanubis_solver-2.0.2/src/google/tpu/kaggle/run.py +83 -0
  39. libanubis_solver-2.0.2/src/google/tpu/kaggle_hashx/run.py +47 -0
  40. libanubis_solver-2.0.2/src/google/tpu/pjrt_c_api.h +3247 -0
  41. libanubis_solver-2.0.2/src/google/tpu/pjrt_common.h +161 -0
  42. libanubis_solver-2.0.2/src/google/tpu/pjrt_probe.c +193 -0
  43. libanubis_solver-2.0.2/src/google/tpu/sha256_pjrt.c +662 -0
  44. libanubis_solver-2.0.2/src/google/tpu/tensor_pjrt.c +802 -0
  45. libanubis_solver-2.0.2/src/google/tpu/tpu_backend.c +997 -0
  46. libanubis_solver-2.0.2/src/google/tpu/tpu_backend.h +66 -0
  47. libanubis_solver-2.0.2/src/google/tpu/tpu_backend_selftest.c +175 -0
  48. libanubis_solver-2.0.2/src/hashx/hashx.c +2524 -0
  49. libanubis_solver-2.0.2/src/hashx/hashx.h +53 -0
  50. libanubis_solver-2.0.2/src/intel/levelzero/argon2id_l0.cl +510 -0
  51. libanubis_solver-2.0.2/src/intel/levelzero/argon2id_l0.spv +0 -0
  52. libanubis_solver-2.0.2/src/intel/levelzero/argon2id_l0.spv.h +1395 -0
  53. libanubis_solver-2.0.2/src/intel/levelzero/hashx_l0.cl +166 -0
  54. libanubis_solver-2.0.2/src/intel/levelzero/hashx_l0.spv +0 -0
  55. libanubis_solver-2.0.2/src/intel/levelzero/hashx_l0.spv.h +537 -0
  56. libanubis_solver-2.0.2/src/intel/levelzero/level_zero/README.md +23 -0
  57. libanubis_solver-2.0.2/src/intel/levelzero/level_zero/ze_api.h +16021 -0
  58. libanubis_solver-2.0.2/src/intel/levelzero/levelzero_argon2.c +649 -0
  59. libanubis_solver-2.0.2/src/intel/levelzero/levelzero_hashx.c +480 -0
  60. libanubis_solver-2.0.2/src/intel/levelzero/levelzero_sha256.c +490 -0
  61. libanubis_solver-2.0.2/src/intel/levelzero/sha256_pow.cl +182 -0
  62. libanubis_solver-2.0.2/src/intel/levelzero/sha256_pow.spv +0 -0
  63. libanubis_solver-2.0.2/src/intel/levelzero/sha256_pow.spv.h +2153 -0
  64. libanubis_solver-2.0.2/src/intel/xe/README.md +258 -0
  65. libanubis_solver-2.0.2/src/intel/xe/intelXe_hashx.xe +32556 -0
  66. libanubis_solver-2.0.2/src/intel/xe/intelXe_sha256.igc.xe +1815 -0
  67. libanubis_solver-2.0.2/src/intel/xe/intelXe_sha256.xe +3108 -0
  68. libanubis_solver-2.0.2/src/mcp/anubis_mcp.c +1307 -0
  69. libanubis_solver-2.0.2/src/nvidia/cuda/README.md +121 -0
  70. libanubis_solver-2.0.2/src/nvidia/cuda/cuda_argon2.cu +688 -0
  71. libanubis_solver-2.0.2/src/nvidia/cuda/cuda_hashx.cu +452 -0
  72. libanubis_solver-2.0.2/src/nvidia/cuda/cuda_sha256.cu +561 -0
  73. libanubis_solver-2.0.2/src/nvidia/cuda/cuda_tensor.cu +368 -0
  74. libanubis_solver-2.0.2/src/nvidia/cuda/kaggle_tensor/README.md +16 -0
  75. libanubis_solver-2.0.2/src/nvidia/cuda/kaggle_tensor/run.py +109 -0
  76. libanubis_solver-2.0.2/src/nvidia/ptx/README.md +264 -0
  77. libanubis_solver-2.0.2/src/nvidia/ptx/cuda_min.h +61 -0
  78. libanubis_solver-2.0.2/src/nvidia/ptx/gen_hashx_ptx.py +388 -0
  79. libanubis_solver-2.0.2/src/nvidia/ptx/gen_opt_ptx.py +346 -0
  80. libanubis_solver-2.0.2/src/nvidia/ptx/hashx_shim.c +57 -0
  81. libanubis_solver-2.0.2/src/nvidia/ptx/kaggle_ab.py +271 -0
  82. libanubis_solver-2.0.2/src/nvidia/ptx/kaggle_bench_hashx_ptx.py +211 -0
  83. libanubis_solver-2.0.2/src/nvidia/ptx/kaggle_bench_ptx.py +157 -0
  84. libanubis_solver-2.0.2/src/nvidia/ptx/kaggle_hashx/run.py +105 -0
  85. libanubis_solver-2.0.2/src/nvidia/ptx/ptx_bench_common.py +68 -0
  86. libanubis_solver-2.0.2/src/nvidia/ptx/ptx_loader.c +868 -0
  87. libanubis_solver-2.0.2/src/nvidia/ptx/ptxsim.py +372 -0
  88. libanubis_solver-2.0.2/src/nvidia/ptx/test_hashx_ptx.py +227 -0
  89. libanubis_solver-2.0.2/src/nvidia/ptx/test_ptx.py +143 -0
  90. libanubis_solver-2.0.2/src/nvidia/sass/README.md +159 -0
  91. libanubis_solver-2.0.2/src/nvidia/sass/argon2id_sm75_kernels.cu +682 -0
  92. libanubis_solver-2.0.2/src/nvidia/sass/hashx_sm75_kernels.cu +741 -0
  93. libanubis_solver-2.0.2/src/nvidia/sass/kaggle_t4_argon2id.py +824 -0
  94. libanubis_solver-2.0.2/src/nvidia/sass/kaggle_t4_hashx.py +1423 -0
  95. libanubis_solver-2.0.2/src/nvidia/sass/kaggle_t4_sass.py +429 -0
  96. libanubis_solver-2.0.2/src/nvidia/sass/sha256_sm75_kernels.cu +236 -0
  97. libanubis_solver-2.0.2/src/opencl/opencl_backend.c +558 -0
  98. libanubis_solver-2.0.2/src/opencl/opencl_kernels.h +1751 -0
  99. libanubis_solver-2.0.2/src/opencl/sha256_pow.cl +196 -0
  100. libanubis_solver-2.0.2/src/vulkan/argon2id.comp +402 -0
  101. libanubis_solver-2.0.2/src/vulkan/argon2id.spv +0 -0
  102. libanubis_solver-2.0.2/src/vulkan/argon2id.spv.h +7208 -0
  103. libanubis_solver-2.0.2/src/vulkan/hashx.comp +180 -0
  104. libanubis_solver-2.0.2/src/vulkan/hashx.spv +0 -0
  105. libanubis_solver-2.0.2/src/vulkan/hashx.spv.h +1449 -0
  106. libanubis_solver-2.0.2/src/vulkan/sha256_comp.comp +223 -0
  107. libanubis_solver-2.0.2/src/vulkan/sha256_comp.spv +0 -0
  108. libanubis_solver-2.0.2/src/vulkan/sha256_comp.spv.h +708 -0
  109. libanubis_solver-2.0.2/src/vulkan/vulkan.c +1517 -0
  110. libanubis_solver-2.0.2/tests/test_core.py +228 -0
  111. libanubis_solver-2.0.2/tests/test_cve_2026_62314.py +283 -0
  112. libanubis_solver-2.0.2/tests/test_local.py +297 -0
  113. libanubis_solver-2.0.2/tests/test_tensor_cuda.py +128 -0
  114. libanubis_solver-2.0.2/tests/test_tensor_v.py +218 -0
  115. libanubis_solver-2.0.2/tests/test_tensor_v_gate.py +238 -0
  116. libanubis_solver-2.0.2/tests/test_versions.py +409 -0
  117. libanubis_solver-2.0.2/third_party/argon2/argon2.c +452 -0
  118. libanubis_solver-2.0.2/third_party/argon2/argon2.h +437 -0
  119. libanubis_solver-2.0.2/third_party/argon2/blake2/blake2-impl.h +156 -0
  120. libanubis_solver-2.0.2/third_party/argon2/blake2/blake2.h +89 -0
  121. libanubis_solver-2.0.2/third_party/argon2/blake2/blake2b.c +390 -0
  122. libanubis_solver-2.0.2/third_party/argon2/blake2/blamka-round-opt.h +471 -0
  123. libanubis_solver-2.0.2/third_party/argon2/blake2/blamka-round-ref.h +56 -0
  124. libanubis_solver-2.0.2/third_party/argon2/core.c +648 -0
  125. libanubis_solver-2.0.2/third_party/argon2/core.h +228 -0
  126. libanubis_solver-2.0.2/third_party/argon2/encoding.c +463 -0
  127. libanubis_solver-2.0.2/third_party/argon2/encoding.h +57 -0
  128. libanubis_solver-2.0.2/third_party/argon2/opt.c +283 -0
  129. libanubis_solver-2.0.2/third_party/argon2/ref.c +194 -0
  130. libanubis_solver-2.0.2/third_party/argon2/thread.c +57 -0
  131. libanubis_solver-2.0.2/third_party/argon2/thread.h +67 -0
  132. libanubis_solver-2.0.2/third_party/argon2-APACHE-2.0.txt +202 -0
  133. libanubis_solver-2.0.2/third_party/hashx-LGPL-3.0.txt +304 -0
  134. libanubis_solver-2.0.2/third_party/nghttp3/include/nghttp3/nghttp3.h +2939 -0
  135. libanubis_solver-2.0.2/third_party/nghttp3/include/nghttp3/version.h +46 -0
@@ -0,0 +1,124 @@
1
+ # Attribution
2
+
3
+ This repository is licensed **MIT + attribution** (see [LICENSE](LICENSE)), with
4
+ two conditions:
5
+
6
+ - **section 3** — the credit line, in one visible place, for any use;
7
+ - **section 4** — if you make silicon from `beyond/`, the DeepSeek logo and the
8
+ credit line **on the chip itself**, big enough to read without squinting.
9
+
10
+ ## The credit
11
+
12
+ Paste this into your README, NOTICE file, about screen, or — for a chip — the
13
+ datasheet and the package marking:
14
+
15
+ ```markdown
16
+ Built with [DeepSeek V4.1 Flash](https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017)
17
+ running [DeepSeek Harness (DSH)](https://github.com/deepseek-ai/deepseek-harness).
18
+ ```
19
+
20
+ Plain text, if markdown is not available:
21
+
22
+ ```
23
+ Built with DeepSeek V4.1 Flash running DeepSeek Harness (DSH).
24
+ ```
25
+
26
+ Both the **model** and the **harness** have to appear. "DeepSeek", "an AI", or
27
+ "automatically generated" on their own does not satisfy the license.
28
+
29
+ ## What counts as use
30
+
31
+ Section 3 of the license is a condition of the grant, so it applies when you:
32
+
33
+ - copy or vendor this code into a project you distribute;
34
+ - ship a binary that links `libanubis_solver.so`;
35
+ - publish a modified version, fork or port;
36
+ - **tape out, synthesise or ship a design derived from `beyond/`** — the Verilog
37
+ is covered too, and section 4 then also requires the marks on the part;
38
+ - redistribute the SASS in `src/nvidia/sass/` or the annotated versions.
39
+
40
+ It does not apply to private use you never distribute, or to quoting this project
41
+ in a review, comparison or paper where you already cite it.
42
+
43
+ ## For a chip: the marks go on the chip
44
+
45
+ A README line is not enough for hardware. Any Silicon Product built from this
46
+ design — an ASIC, a chiplet, a multi-die assembly, an FPGA board or module, a
47
+ configuration image — has to carry the logo and the line in the three places
48
+ below. This is section 4 of the [license](LICENSE), not a request.
49
+
50
+ | where | what | minimum size |
51
+ |---|---|---|
52
+ | die (every die you fabricate) | the logo and the line, in a visible in-die layer | legible at 100x optical inspection |
53
+ | package / module marking | the logo **and** the line, as type (wrapping is fine) | line cap height ≥ 1.2 mm, logo ≥ 3.0 mm wide; on a face under 8 mm across, 0.9 mm and 2.0 mm |
54
+ | datasheet, first page or cover | the logo and the line | line cap height ≥ 4 mm (≈ 12 pt) |
55
+ | product page (if you have one) | the logo and the line | normal body size or larger |
56
+
57
+ The naked-eye test is the point of the numbers: a person with normal corrected
58
+ vision must be able to read the whole line on the part without a magnifier and
59
+ without leaning in. On a part that ships with a permanently attached heatsink,
60
+ lid, shield or enclosure, the same marks go on the outer surface too. A QR code,
61
+ barcode, URL or serial number on its own does not satisfy it — the line has to be
62
+ type.
63
+
64
+ The logo is [`docs/img/deepseek-logo.svg`](docs/img/deepseek-logo.svg): the
65
+ official lockup, whale and wordmark together, and it stays together — the whale
66
+ alone is not the logo. Keep its shape and proportions; black on light and white
67
+ on dark are both fine, and in a one-layer in-die mark the whale's eye is simply
68
+ a cutout. Stretching, cropping, rotating, mirroring or redrawing is not.
69
+
70
+ The die carries the logo; the package and the datasheet carry the logo and the
71
+ line. The line is tiny in metal, which is why the package is what has to be
72
+ readable at arm's length.
73
+
74
+ For an FPGA or a board you assemble but do not fabricate: mark the board, module
75
+ or enclosure you ship, plus the datasheet. You do not own the FPGA's package, so
76
+ that is not what the condition asks for.
77
+
78
+ For a design you hand to a foundry: put the marks in the GDS you hand over —
79
+ metal-layer text and the logo are normal parts of a die — and in the datasheet.
80
+ GDSII, netlists, bitstreams and the RTL are "Software" under section 3 as well,
81
+ so the credit line applies on top of the marks.
82
+
83
+ ### Checklist before you ship a part
84
+
85
+ - [ ] line in the die, readable at 100x
86
+ - [ ] logo in the die, proportions unchanged
87
+ - [ ] line and logo on the package marking, line ≥ 1.2 mm cap height
88
+ - [ ] logo ≥ 3.0 mm wide on the package
89
+ - [ ] marks on the heatsink/lid/shield if it is permanently attached
90
+ - [ ] datasheet first page carries both, line ≥ 4 mm
91
+ - [ ] exact wording: `Built with DeepSeek V4.1 Flash running DeepSeek Harness (DSH)`
92
+ - [ ] nothing in the datasheet suggests DeepSeek endorses the part
93
+
94
+ The RTL already carries the line in the top-level module headers
95
+ (`beyond/rtl/top/anubis_argon2_card.v`, `beyond/rtl/top/anubis_tri_chip.v`).
96
+ Keep it there — and add the marks to the part, which is the part a header comment
97
+ cannot do for you. Removing either from a derivative design is exactly what the
98
+ license forbids.
99
+
100
+ The DeepSeek name and logo belong to their owner. Section 4 requires their use
101
+ only to identify where the design came from, and grants no trademark rights
102
+ beyond that; it does not imply endorsement.
103
+
104
+ ## Third-party parts keep their own licenses
105
+
106
+ The attribution and marking conditions are on top of the existing terms, and
107
+ cannot loosen them. `src/hashx/hashx.c` is **LGPL-3.0** (a port of tevador/hashx)
108
+ and `third_party/argon2` is **CC0-1.0 / Apache-2.0**. See
109
+ [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md): the LGPL portion in particular
110
+ carries obligations well beyond attribution.
111
+
112
+ ## Why this condition exists
113
+
114
+ The work in this repository — the C engine, the GPU kernels and their SASS, the
115
+ bindings, the Verilog — was produced in one session by DeepSeek V4.1 Flash
116
+ driving DeepSeek Harness. Requiring the credit is a way of keeping that
117
+ provenance attached to the result, and for software it costs whoever uses it one
118
+ line. For silicon it costs a bit of die area and a few millimetres of package
119
+ marking, which is the whole point: a chip outlives the README it was generated
120
+ from.
121
+
122
+ If these conditions block a use you need — an internal policy that forbids such
123
+ credits, or a downstream license that conflicts — ask the copyright holders for a
124
+ separate grant rather than dropping the notice.
@@ -0,0 +1,168 @@
1
+ MIT License, with attribution and silicon-marking requirements
2
+ ================================================================
3
+
4
+ Copyright (c) 2026 anubis-solver contributors
5
+
6
+ This is the MIT license text with TWO added conditions (sections 3 and 4 below).
7
+ Because of those conditions it is not the unmodified MIT license: refer to it as
8
+ "MIT + attribution" or "MIT-Attribution", not as plain "MIT". If you need an
9
+ unencumbered license for a use these conditions make awkward, ask the copyright
10
+ holders for a separate grant - they may give one.
11
+
12
+ --------------------------------------------------------------------------------
13
+
14
+ 1. Permission
15
+
16
+ Permission is hereby granted, free of charge, to any person obtaining a copy of
17
+ this software and associated documentation files (the "Software"), to deal in
18
+ the Software without restriction, including without limitation the rights to
19
+ use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
20
+ the Software, and to permit persons to whom the Software is furnished to do so,
21
+ subject to the conditions below.
22
+
23
+ 2. Notice
24
+
25
+ The above copyright notice and this permission notice shall be included in all
26
+ copies or substantial portions of the Software.
27
+
28
+ 3. Attribution
29
+
30
+ This condition is a condition of the grant in section 1. Any permission granted
31
+ above is conditioned on the following being satisfied by anyone who uses,
32
+ copies, modifies, merges, publishes, distributes, sublicenses, sells, or builds
33
+ hardware from the Software or a derivative work:
34
+
35
+ (a) They must credit the tooling that produced this work, in the form
36
+
37
+ Built with DeepSeek V4.1 Flash running DeepSeek Harness (DSH)
38
+
39
+ or the shorter, equivalent form
40
+
41
+ Made with DeepSeek V4.1 Flash on DSH
42
+
43
+ (b) The credit must be reasonably visible to the recipient of the Software or
44
+ of the hardware built from it. Any ONE of the following is sufficient:
45
+
46
+ - the README or the top-level documentation of the project that uses it;
47
+ - a NOTICE, CREDITS or attribution file shipped with it;
48
+ - an "about", "credits" or "acknowledgements" screen, page or section, if
49
+ the project has one;
50
+ - for a hardware design: the top-level RTL module header comments, the
51
+ register-map or datasheet document, or the package/die documentation -
52
+ wherever the design credits its other contributors.
53
+
54
+ Silicon is stricter than this: a Silicon Product must also satisfy
55
+ section 4, and where the two overlap section 4 wins.
56
+
57
+ (c) The credit must name both things: the model and the harness. "DeepSeek",
58
+ "an AI", or "automatically generated" alone does not satisfy this
59
+ condition. Keeping the hyperlinks to
60
+ https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017 and
61
+ https://github.com/deepseek-ai/deepseek-harness next to the credit
62
+ satisfies it as well.
63
+
64
+ (d) The credit must not be used to suggest that the copyright holders or
65
+ DeepSeek endorse, sponsor, or take responsibility for the project that
66
+ uses it.
67
+
68
+ 4. Silicon attribution: the marks go on the chip
69
+
70
+ This condition is a condition of the grant in section 1, in addition to
71
+ section 3. It applies to every Silicon Product: any integrated circuit, die,
72
+ chiplet, multi-die assembly, packaged part or module, and any FPGA or other
73
+ programmable-device configuration image, that is made from, implements, or
74
+ contains the Software, a derivative work, or any part of `beyond/` (its RTL, its
75
+ testbenches, and the designs they describe). Anyone who makes, has made, sells,
76
+ transfers or otherwise distributes a Silicon Product (the "maker") must:
77
+
78
+ (a) Put the DeepSeek logo and the line from (b) on the Silicon Product
79
+ itself:
80
+ - on every die the maker has fabricated (for a multi-die assembly: on
81
+ each of those dies), as in-die marks in a visible layer; and
82
+ - on the package or module. Where the maker does not make the package
83
+ itself - an FPGA-based board, a chiplet in a third party's package -
84
+ the equivalent mark goes on the board, module or enclosure the maker
85
+ does ship.
86
+ The logo is the official DeepSeek lockup included with this repository at
87
+ `docs/img/deepseek-logo.svg`: the whale mark and the wordmark together.
88
+ Its shape, proportions and the relative position of the two must be
89
+ unchanged. Monochrome is fine and the ink may follow the surface (black on
90
+ light, white on dark); in a single-layer in-die mark, the whale's eye is a
91
+ cutout, which is not a change of shape. The logo must not be stretched,
92
+ squashed, rotated, mirrored, cropped, redrawn, or split so that the whale
93
+ appears without the wordmark.
94
+
95
+ (b) Put this line on the package marking, in full and as type:
96
+
97
+ Built with DeepSeek V4.1 Flash running DeepSeek Harness (DSH)
98
+
99
+ It must be readable as text: a QR code, barcode, URL, serial number or a
100
+ document the part merely points to does not satisfy this paragraph on its
101
+ own.
102
+
103
+ (c) Put the same logo and the same line on the datasheet, on its first page
104
+ or cover, and on the product page if the maker publishes one.
105
+
106
+ Size and legibility. The test is that a person with normal corrected vision
107
+ can read the whole line without a magnifier and without squinting. The line
108
+ may be wrapped over several lines; the cap height below applies to each line.
109
+
110
+ - package or module: the line at a cap height of at least 1.2 mm and
111
+ the logo at least 3.0 mm wide, on a face that is normally visible
112
+ when the part is installed. On a package whose marked face is
113
+ smaller than 8 mm across - where those numbers cannot physically
114
+ fit - the floor is a 0.9 mm cap height and a 2.0 mm logo, still as
115
+ type. If the part ships with a permanently attached heatsink, lid,
116
+ shield or enclosure, the same marks must appear on its outer surface
117
+ as well;
118
+ - die: the logo and the line present and legible under standard optical
119
+ inspection at 100x. Naked-eye legibility is carried by the package and
120
+ the datasheet, because an in-die mark is microscopic by nature;
121
+ - documentation: the line at a cap height of at least 4 mm (about
122
+ 12 pt), in a colour that contrasts with the background, on the first
123
+ page or cover - not only in a footnote or end-credits page, and not
124
+ smaller than the body text used for the document's other credits.
125
+
126
+ (d) A Silicon Product distributed without the marks required by (a), (b) or
127
+ (c) is not licensed under this license. Note also that GDSII, OASIS, mask
128
+ sets, netlists, bitstreams, HDL and the RTL in `beyond/` are "Software"
129
+ for the purposes of section 3, so the credit there applies to them as
130
+ well.
131
+
132
+ (e) The DeepSeek name and logo are the property of their owner. This
133
+ condition requires their use solely to identify the provenance of the
134
+ design and grants no trademark rights beyond that use; it does not imply
135
+ endorsement (see 3(d)).
136
+
137
+ 5. Not required
138
+
139
+ Sections 3 and 4 do not apply to: private use that is not distributed or made
140
+ available to anyone outside the organisation using it; quoting a portion of this
141
+ Software in a discussion, review, benchmark comparison or academic work, where
142
+ citing the project is already normal practice; or private, undistributed
143
+ engineering samples, shuttle runs and internal qualification parts that are never
144
+ sold, given away or otherwise transferred outside the organisation.
145
+
146
+ 6. Conditions from other licenses still apply in full
147
+
148
+ Portions of this repository are licensed differently and their terms are
149
+ unaffected by sections 3 and 4 - in particular `src/hashx/hashx.c`
150
+ (**LGPL-3.0**, from tevador/hashx) and `third_party/argon2` (CC0-1.0 /
151
+ Apache-2.0). See THIRD_PARTY_NOTICES.md. Where a third-party license conflicts
152
+ with section 3 or 4, that licence wins for the third-party portion.
153
+
154
+ 7. Warranty
155
+
156
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
157
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
158
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
159
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
160
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
161
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
162
+ SOFTWARE.
163
+
164
+ --------------------------------------------------------------------------------
165
+
166
+ See ATTRIBUTION.md for a paragraph you can paste into your own README, the
167
+ checklist for marking a chip, and what "the Software or a derivative work"
168
+ covers in practice.
@@ -0,0 +1,8 @@
1
+ include Makefile
2
+ include LICENSE ATTRIBUTION.md THIRD_PARTY_NOTICES.md README.md
3
+ include pyproject.toml setup.py
4
+ recursive-include include *.h
5
+ recursive-include src *.c *.h *.s *.S *.comp *.cl *.cu *.spv *.spv.h *.xe *.py *.md
6
+ recursive-include third_party *.c *.h *.txt
7
+ recursive-include _anubis_solver_native *.so *.py
8
+ global-exclude *.o *.a *.d *.so *.dylib