conding
Usage
from conding.dune.tec import TECDashboard
tec = TECDashboard()
tec.market_information.holders_distribution()
Unable to display output for mime type(s): application/javascript, application/vnd.holoviews_load.v0+json
Unable to display output for mime type(s): application/javascript, application/vnd.holoviews_load.v0+json
<style>.bk-root, .bk-root .bk:before, .bk-root .bk:after {
font-family: var(--jp-ui-font-size1);
font-size: var(--jp-ui-font-size1);
color: var(--jp-ui-font-color1);
}
</style>
| rank_number | address | balance | perc | cumulative_perc | |
|---|---|---|---|---|---|
| 0 | 1 | <a href="https://blockscout.com/xdai/mainnet/a... | 1.500717e+05 | 8.264853e-02 | 0.082649 |
| 1 | 2 | <a href="https://blockscout.com/xdai/mainnet/a... | 1.060533e+05 | 5.840639e-02 | 0.141055 |
| 2 | 3 | <a href="https://blockscout.com/xdai/mainnet/a... | 7.383866e+04 | 4.066494e-02 | 0.181720 |
| 3 | 4 | <a href="https://blockscout.com/xdai/mainnet/a... | 6.933751e+04 | 3.818603e-02 | 0.219906 |
| 4 | 5 | <a href="https://blockscout.com/xdai/mainnet/a... | 5.916598e+04 | 3.258430e-02 | 0.252490 |
| ... | ... | ... | ... | ... | ... |
| 540 | 541 | <a href="https://blockscout.com/xdai/mainnet/a... | 1.024000e-15 | 5.639443e-22 | 1.000000 |
| 541 | 542 | <a href="https://blockscout.com/xdai/mainnet/a... | 2.560000e-16 | 1.409861e-22 | 1.000000 |
| 542 | 543 | <a href="https://blockscout.com/xdai/mainnet/a... | 8.000000e-17 | 4.405815e-23 | 1.000000 |
| 543 | 544 | <a href="https://blockscout.com/xdai/mainnet/a... | 1.600000e-17 | 8.811630e-24 | 1.000000 |
| 544 | 545 | <a href="https://blockscout.com/xdai/mainnet/a... | 1.000000e-18 | 5.507269e-25 | 1.000000 |
545 rows × 5 columns
tec.abc_tributes.tribute_distribution()
| date | action | sum(tribute) | tribute_total | |
|---|---|---|---|---|
| 0 | 2022-04-01T00:00:00Z | Sell | 364.927505 | 96097.104858 |
| 1 | 2022-05-01T00:00:00Z | Buy | 502.690920 | 96097.104858 |
| 2 | 2022-05-01T00:00:00Z | Sell | 27525.756009 | 96097.104858 |
| 3 | 2022-06-01T00:00:00Z | Buy | 18.424300 | 96097.104858 |
| 4 | 2022-06-01T00:00:00Z | Sell | 9637.008165 | 96097.104858 |
| 5 | 2022-07-01T00:00:00Z | Buy | 46.280000 | 96097.104858 |
| 6 | 2022-07-01T00:00:00Z | Sell | 875.231330 | 96097.104858 |
| 7 | 2022-08-01T00:00:00Z | Buy | 84.000440 | 96097.104858 |
| 8 | 2022-08-01T00:00:00Z | Sell | 3578.698760 | 96097.104858 |
| 9 | 2022-09-01T00:00:00Z | Buy | 440.034000 | 96097.104858 |
| 10 | 2022-09-01T00:00:00Z | Sell | 6524.963118 | 96097.104858 |
| 11 | 2022-10-01T00:00:00Z | Buy | 0.448273 | 96097.104858 |
| 12 | 2022-10-01T00:00:00Z | Sell | 7265.726778 | 96097.104858 |
| 13 | 2022-11-01T00:00:00Z | Buy | 42.080000 | 96097.104858 |
| 14 | 2022-11-01T00:00:00Z | Sell | 7948.406669 | 96097.104858 |
| 15 | 2022-12-01T00:00:00Z | Buy | 1.260000 | 96097.104858 |
| 16 | 2022-12-01T00:00:00Z | Sell | 6767.473366 | 96097.104858 |
| 17 | 2023-01-01T00:00:00Z | Buy | 0.310000 | 96097.104858 |
| 18 | 2023-01-01T00:00:00Z | Sell | 3886.310413 | 96097.104858 |
| 19 | 2023-02-01T00:00:00Z | Buy | 0.100000 | 96097.104858 |
| 20 | 2023-02-01T00:00:00Z | Sell | 4413.471438 | 96097.104858 |
| 21 | 2023-03-01T00:00:00Z | Buy | 3.100000 | 96097.104858 |
| 22 | 2023-03-01T00:00:00Z | Sell | 13877.419531 | 96097.104858 |
| 23 | 2023-04-01T00:00:00Z | Buy | 460.600000 | 96097.104858 |
| 24 | 2023-04-01T00:00:00Z | Sell | 1832.383842 | 96097.104858 |
Installation
Installing as a Package
pip install:
pip install conding
Export your Dune API Key as an environment variable.
export DUNE_API_KEY='<Your Key>'
Local Development
Clone the repository
git clone git@github.com:bonding-curves/conding.git
cd conding
Add your Dune API Key to the .env file.
mv .env.template .env
vi .env
Install the requirements with poetry. For instructions on installing poetry see: https://python-poetry.org/docs/
poetry install --with dev
poetry shell
Using NBDev
When first running the package, install git hooks and quarto
nbdev_install_hooks
nbdev_install_quarto
Run tests with nbdev
nbdev_test
View documentation locally
nbdev_preview
Export changes made to notebooks
nbdev_export
Build Documentation
nbdev_docs
See more options
nbdev_help
See https://nbdev.fast.ai/ for more information on Nbdev.
Metadata
Release files for conding 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| conding-0.1.3.tar.gz | 18.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| conding-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.0 kB
Release files / conding-0.1.3.tar.gz
| Download URL | conding-0.1.3.tar.gz |
|---|---|
| Size | 18.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3bce8a66d57708cac87e64dd67bb0d22713111b4e5ea9e5155b477bb73bcd974
|
|
BLAKE2b-256 checksum How to use checksums |
df6fbb1af58e69404671d2ce451be9ca159c9bf32a52afdeb8cd020e3a17eb68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Release files / conding-0.1.3-py3-none-any.whl
| Download URL | conding-0.1.3-py3-none-any.whl |
|---|---|
| Size | 17.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3d0db0f661a73f4161da065a7b9e476ea537ac782cd3e7ee5181076e10b81903
|
|
BLAKE2b-256 checksum How to use checksums |
405958d231e3330d232f971ca865be0064b7683d6ecb86c1a466cc9596027aff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Security for conding 0.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.