MemPool: --- SART

ABOUT SART

SART is still in alpha and may not work as expected - use at your own risk!

Description

SART is an application designed for advanced use and research of the Arweave blockchain, acting as a content discovery, statistics and management (CDSM) utility. It assumes that the user is familiar with the permaweb and has at least some idea of what they're doing.

You have control. Use it responsibly.

CAUTION

Anyone can upload data into Arweave - the data stored is decentralized, permanent and immutable.

As such, the content that can be discovered with this application may be harmful, shocking, sexual, controversial, political or even illegal. Exploring the data in Arweave should not be done by children or sensitive adults and utmost care should be taken when doing so while living in repressive countries (such as North Korea, Russia or United Kingdom).

Validity of the data that is obtained from gateways is not yet verified.

Disclaimer

SART is a computer program that can be used to interact with Arweave.

It is not a service - no guarantees are given regarding this interaction. The data accessible with it is stored in Arweave and is beyond the control of the developer. The use of the application may result in monetary loss and/or other undesired consequences.

SART is provided as-is and it is not yet production-ready - everything is still under construction and subject to change. This version should be considered as a mere sneak-peek at its development for the sake of historic preservation.

This application might make network requests to third-party servers (including but not limited to arweave.net and other Arweave-gateways) that may log and utilize the data they obtain.

SART is not affiliated with anyone at this point in time.

Sections

FilesBrowse and view files and other data that people have uploaded into Arweave.
QueryQuery for Arweave-transactions using GraphQL. For advanced users.
UploadDisabled for now - is operational but needs some additional work. The bold ones wishing to test it regardless, mouseover here.
StatusGet the status, price and pending transactions from the Arweave-network.
StarGridContains a rudimentary replay viewer for the game StarGrid. Player stats, search and leaderboards currently inoperative due to some issues with the AO testnet compute unit.
UtilContains utilities such as value converters and an ArNS-resolver.

Controls (File Manager)

Arrow keysSelect item
BackspaceTraverse to parent directory
EnterAccess the selected item
TOpen the selected item in a new tab
VView the selected item
EEnter the selected item (if container)
P / SpacePlay/pause the selected media item
Mouse clickSelect item
Double-clickAccess item
Middle-clickOpen in new tab (if able)
MouseoverShow tooltip if present (currently displayed by the browser)
Drag cornerDrag the bottomright corner of the sidebar in File Manager to resize it - unintuitive, I know.

(These will eventually be bindable)

Known issues

2026-03-15
  • Arweave.net: The gateway may currently fail to return the data of some transactions (and acting up in other areas as well), the issue related to it being migrated to HyperBEAM.
  • ArFS: Not all metadata-transactions are fetched for drives found with 'All content', leading to possible undetected Drive-Id collisions, yet even in this case it should show content of just one address.
  • ArFS: The browser may crash to memory-related issues while loading a large drive snapshot (there's a 1GB-one that results in this).
  • Data Export: Exporting large amount of data may fail to 'RangeError: Invalid string length'; the export data format is far from optimal.
  • File Manager: The view-mode 'Advanced' is not optimal (uses the same table as the query-section) - might completely rework it.
  • File Manager: The 'Advanced' tab elements sometimes glitch when multiple sections are open.
  • File Manager: Loading large images for the icons-view can slow down the browser - might add an option for sequential loading + use smaller thumbnails when able.
  • File Manager: The DOM gets overwhelmed by nodes with extremely large amount of items; will implement pagination and/or virtual scrolling at some point.
  • Generic: People are storing a lot of similar mass-produced garbage in Arweave instead of using it to preserve a wider variety of material.
  • Status: 'Ready' is sometimes displayed even while an operation is active.

Roadmap

  • Add proper details-like view (consisting of columns) to the File Manager.
  • Add a tree view for nested data and a filesystem tree view to the File Manager.
  • Add ArNS- and AO-related nodes to the File Manager.
  • Add support to inspect the logs and logged data with the ability to import them.
  • Make section-local settings persistent as well.
  • Add a section for querying for blocks along with also using the HTTP API to display TX and block info.
  • Improve the Query/Transactions section by adding tabs, allowing custom written queries, displaying effective query and its result, adding support for wildcard for tag values, grouping different tag values into the same tag-item and allowing custom tag object fields for future compatibility.
  • Add support for advanced searching/filtering to the File Manager.
  • Add support for uploading and other file operations to the File Manager.
  • Add an option to batch-fix the incorrect file modified times made by old versions of ArDrive.
  • Add an option to deep-scan for missing ArFS-drives (ones lacking drive metadata due to the past times of network congestion).
  • Add support for interacting with private ArFS-drives and Akord-vaults.
  • Implement the option to refresh the view of GraphQL-based SVFS-nodes by retrieving the changes that have taken place after the initial populating.
  • Implement the timetravel-option by limiting the nodes' metadata to that which exists at or before the chosen time/block height.
  • Add an option to recursively populate all the contained nodes in File Manager.
  • Implement the flat view in File Manager.
  • Add an option to load the thumbnail-images sequentially in File Manager and the ability to reload them if failed.
  • Add a 'back' navigation feature to the File Manager.
  • Add support for selecting multiple items to File Manager along with a proper statistics-display for the nodes.
  • Implement caching of the SVFS-tree (the virtual filesystem) of the File Manager.
  • Extend ArFS or implement an additional format for adding symlinks (that can point to drives, files, directories, other SVFS-locations or external URLs) and a richer metadata-features (such as titles and descriptions in multiple languages, graphical overlay-layers for notes to media content and appearance-related hints) along with the ability for people to leave comments on files (with some prerequisites).
  • Add EXIF-support to the file-nodes of the File Manager (could also be done with the plugin system).
  • Add tabs to the File Manager.
  • Implement per-location sort settings (and possibly view-settings as well) to the File Manager.
  • Add an option to treat the current File Manager location as trusted (until its content changes) to selectively enable insecure things (such as embedding PDF-documents and using iframes with more relaxed sandbox-setting).
  • Add a global right-click context menu and a better tooltip-system.
  • Add settings to configure the keybinds.
  • Add an utility for working with path manifests.
  • Add additional "gadgets" that can be added to the top bar, such as additional data displays and a music player.
  • Add support for persistent bookmarks (TXIDs, Drive-IDs etc.) and custom color profiles (even though black and red ought to be enough for anybody).
  • Add support for user-created custom SVFS-nodes for File Manager and allow modification of GQL-queries for the existing ones.
  • Make the config and IndexedDB browseable via the local node of File Manager
  • .
  • Implement a plugin/addon system (thinking of WASM) for dealing with unsupported data and file formats allowing users to extend the functionality of the application, for example to view flash-animations, play tracker music and browse the content of archives and disk images.
  • Add a forum/bulletin board (that could also be distributed as standalone) and either a separate or integrated messaging functionality.
  • Add an option to test all the added gateways and network peers to see which have the desired data (such as TX).
  • Add utilities to interact with AO with the ability of locally evaluating the process-states (when feasible).
  • Maybe evaluate SmartWeave as well if this can be done safely in a sandbox (with a WASM-based JS-interpreter?).
  • Add the ability to export data in various formats (CSV, XML, ODS etc.)
  • Add local private key management as an alternative to external wallets.
  • Add an option to view and log the list of network peers.
  • Rework the layout of the sections About and Status.
  • Move StarGrid from its own section to a File Manager node.
  • Add a more comprehensive information section.
  • Add a classic icon view (with the ability to freely position icons) and support for custom icon sets to File Manager.
  • Add advanced options to customize the layout of the application - a proper theme support, perhaps.
  • Create relay software that could extend the SFVS by allowing access to network protocols unreachable by the browser (like FTP/SFTP) and maybe external services (like Google Drive and Dropbox) if accessing these isn't practical without third-party libraries.

Addresses

sart Live versionArweave ArNSLeased
sart_silanael Live versionArweave ArNSPermanent
sart_silaproductions Live versionArweave ArNSPermanent
SARTPCqxZh6XR_KmDBBxP9SvJplkNYe6_18Y1P0EuqcUpload-fees and donationsArweave addr.Permanent

External libraries used

Arweave-JS: Only used for uploading (prior to implementing a native signer and uploader), not loaded by default.

Designed for

Network arweave.N.1 version 5, release 89
Arweave-gateway AR.IO release 45-pre (newest ar-io-node is v72), Arweave.net ported to HyperBEAM (currently has issues)
GraphQL-schema Found at TXID gIVNXHpIpg1R0pkdLYOQslP5qNd0I8-WTuINg2HfTBA
Web browser Chromium 145.0.7632.75 (AppImage) and 138.0.7204.92 (AppImage)
Wallet-extension Wander 1.41.3
Display-resolution 1920x1080 and 1280x1024
Operating system Linux Mint 22 Cinnamon 6.2.9 (X11)

Author

NameSilanael
Typeperson
AboutI'm a hobbyist developer with a passion for data preservation (and an aspiration to start making a living with it).

Having been engraving parts of my soul into Arweave ever since 2021, I've set out to do what I can to make the permaweb prosper; the SART-project is a stepping stone towards that goal, one created with the amount of care and reverence necessary whenever working with permanent data.

I tend to write as much from scratch as is feasible, feeling that a proper understanding of these systems is imperative for their safe and effective use - something that also acts to decrease the risk for external vulnerabilities.

ArweavezPZe0p1Or5Kc0d7YhpT5kBC-JUPcDzUPJeMz2FdFiy4 (primary) and SilaP1T6g4vqzkZa-LJTmNmd06v5tNLB7AAR3di3SzM (releases)
ArNSsilanael
ANSsilanael.ar
Web2silanael.com
E-mailsila at silanael dot com
DiscordSilanael (Silanael#2691)
Contact viaE-mail or Discord

Changelog


0.7.1-ALPHA

2026-03-15, block height 1876688
  • NEW: File Manager: Nodes 'Full content' and 'Snapshots' added to ArFS-drives; the former allows for faster drive access if a drive snapshot is available (it uses the newest snapshots as the base and queries for changes made after it), while the latter lists and directly accesses the content of drive snapshots.
  • NEW: The path in File Manager is now present in the URL, allowing for sharing links to locations. It will try to populate its way to the target location. Linking to custom addresses added to '/arweave/address' is supported as well. (Following the path from the URL can be disabled with setting 'AllowPathInURL' and the setting 'AlterURLArguments' can be used to prevent SART from modifying the URL)
  • NEW: GraphQL: The query template for transaction-queries can now be customized or chosen from a set of templates.
  • NEW: File Manager: Can now choose whether to display info for the current or the selected item, or have this decided automatically.
  • NEW: File Manager: View mode 'compact' implemented.
  • NEW: File Manager: 'Display as': A rudimentary hex editor (or rather a hex viewer) added.
  • NEW: File Manager: 'Display as': Preliminary checksum calculation added (just SHA-256 and SHA-512 for now).
  • NEW: File Manager: 'Display as': Can now be set to 'none' to disable displaying the node data in the viewer (can still open them in new tabs).
  • NEW: File Manager: Can now choose whether to display thumbnails or not (using the 'TN' checkbox). This can be cycled to reload images that failed to load or disabled as an additional security-measure.
  • CHANGE: File Manager: 'Raw files' renamed to 'Simple files' for the sake of clarity.
  • CHANGE: File Manager: Changed a few icons in the Icons-mode. These are currently unicode-symbols - will finish making custom graphical icons at some point.
  • NEW: File Manager: Can now export the filesystem-tree (SVFS) into a file. Use with caution. The format will likely be changed if I end up overhauling the node structure (which I've been planning of doing), so don't get too attached to it. The export-files can be browsed at Local System -> SVFS-imports.
  • NEW: Data Logging: Can now export the network price log.
  • NEW: Settings: The config can now be saved and loaded, yet the format and structure are still subject to change.
  • CHANGE: Data Logging: Altered the mempool-log export format to match what I'm using with other exports.
  • NEW: Security: Settings: Added settings to selectively disable <img>, <video>, <audio> and <canvas> (in addition to the already existing <iframe>) - this is mostly an emergency security-measure to disable the use of an element if there's an unmitigated exploit related to it, perhaps also useful if one wishes to use an older version of SART and the browser version that supports it has a vulnerability related to a tag.
  • NEW: File Manager: Added an option to access items on click instead of selecting them (along with an option to open in new tab) - devices with a touchscreen (determined by the ability to hover) should have this as the default.
  • NEW: File Manager: Items now have mouseover-tooltips ('title' attribute, handled by the browser).
  • NEW: File Manager: NeedsArNS-tweets can now also be viewed as grouped by author, archivist or date. They can also be entered to inspect the files in the path manifest.
  • NEW: Settings: The transaction query template can now be edited - it is used by sections Files and Query/Transactions. This was added so that older versions of SART can continue to function even if the GraphQL-scheme undergoes some breaking changes in the future. The modifications to the template are not yet saved and will not persist after page reload.
  • NEW: Settings: The list of gateways can now be reset to default.
  • NEW: Settings: Added settings 'GQLURLOverride', 'GQLEndpoint' and 'SVFSNodesInMultiplePlaces'. The former can be used to fully control the URL of GraphQL-queries - perhaps useful if AO-based querying becomes a thing - while the latter can be disabled if having SVFS-nodes contained in many locations causes issues (this is currently only done by the ArFS snapshot-nodes).
  • NEW: Settings: Added setting 'Confirm when parsing JSONs large than X bytes' to attend to the issue of response.json () currently crashing the tab to SIGILL on Chrome 145.0.7632.75 (Linux Mint) if the JSON is too large (happens with 1GB ArFS-snapshot at TXID Cox9InUmZDpYN3uhOUv29AsYqMiQX9liVMErOv-qVN4). The setting currently only applies to path manifests and ArFS-snapshots - the default value is 536870912 (512MB).
  • NEW: Settings: Added setting 'Block-Overlap' to set the amount of overlapping blocks that will be queried for when supplement existing/previously fetched content. The value 0 means no overlap, ie. querying with minimum block height being one block after the last block that we had some existing data in. I feel that having no overlap might risk missing some transactions as there might be a situation where not all the content of the latest block was properly indexed by the time the previous data was retrieved - I could see this happening where a fresh block has both native and bundled transactions, the former not yet available. I'm currently only using this setting when querying for ArFS metadata-changes made after the snapshot that's used as a base, but will likely use it as well when refreshing a GraphQL-using node. The default value 30 amounts to over an hour with 2.5min average block times - time enough for everything to be indexed, one would hope.
  • NEW: Arweave-links (ones pointing to TXIDs or ArNS-names) will now be updated when the active gateway changes. This can be disabled in Settings.
  • NEW: Settings: New settings added: 'Disable hotkeys when an input-element is focused' and 'Ask for confirmation when exporting personal data'.
  • NEW: Query/Transactions: Tag-groups added for Do-Not-Store-requests, address-vouches, Alex. archives and DeRadar air traffic snapshots.
  • FIX: File Manager: The sidebar no longer resets when changing node or view mode.
  • FIX: Keyboard navigation now works in Media Browser even after invoking fullscreen with doubleclicking.
  • FIX: File Manager: The keyboard shorcuts 'T' (open in new tab), 'E' (enter node) and 'V' (view node) now work in media view as well.
  • FIX: Image thumbnails now work for local files.
  • CHANGE: The default values for log-levels for Status-bar and Console changed to verbose and info respectively - found that console.log can slow everything down quite a bit. These settings will not automatically change if you've ran SART before this version.
  • CHANGE: File Manager now spans the entire height of the screen + content no longer goes below the horizontal control bars (changed the main layout to a more sensible flexbox-based one).
  • CHANGE: File Manager: 'View as' selector is now universally present in the sidebar (was only in the media browser) and will now reset to 'auto' when the displayed node changes (unless LOCK is checked).
  • CHANGE: The status-bar (the one at the bottom) now has a maximum height.
  • CHANGE: Settings: Gateways 'https://turbo-gateway.com', 'https://ar-io.dev' and 'https://ardrive.net' added to the default gateway list (was going to add ar-io.net as well but it got shut down). Considering adding https://arweave-search.goldsky.com (Goldsky).
  • CHANGE: GraphQL: Some shenaningans regarding 'BlockFilter' and 'RangeFilter' - for a brief moment, BlockFilter wasn't working, gateways expecting RangeFilter instead. After having brought it up, now RangeFilter no longer works on non-GoldSky-gateways. If the queries start failing, try changing between 'RangeFilter' and 'BlockFilter' for the TX-query template in SETTINGS to see if either works. (Goldsky's GraphQL-schema here and the one live at arweave.net/graphql - one that this version of SART uses - here)
  • CHANGE: Security: Now freezing 'Object.prototype'.
  • Developed and tested on Chromium 145.0.7632.75 (x86-AppImage at TXID:14pYYI7IUWT6VjIbM1kPKqxVDVQKtvjbxO-ueOn8TTc) using Linux Mint 22 Cinnamon, X11. Supported Arweave-network: version 5, release 89, AR-IO gateway software: 45-pre (newest v70), Wallet-extension: Wander 1.41.3, GraphQL-schema: TXID:gIVNXHpIpg1R0pkdLYOQslP5qNd0I8-WTuINg2HfTBA

0.7.0-ALPHA

2026-02-02, block height 1848886
  • NEW: File Manager: Can now browse all the content in Arweave. Proceed with caution.
  • NEW: File Manager: Custom Arweave-addresses can now be added and browsed. ArNS not yet supported nor are the added entries saved.
  • NEW: File Manager: Preliminary support for Akord-vaults, path manifests, archived tweets (PermaButler and NeedsArNS) and raw transactions/files added.
  • NEW: File Manager: The amount of query-retries can now be incremented for the active step.
  • NEW: File Manager: Keyboard can now be used for navigation and control (even when browsing images fullscreen).
  • NEW: File Manager: Preliminary PCX-image support added.
  • NEW: File Manager: Advanced-tab added.
  • FIX: File Manager: The sequence controls now work more often than they used to. Still highly a work in progress.
  • FIX: Generic: Date-strings will now be empty (null) if the source value is not set or not a number.
  • NEW: Settings: GraphQL-related config as well as per-node configuration added (accessible via the File Manager), allowing setting the query direction and the maximum amount of edges to fetch (the actual amount of items may differ).
  • NEW: Util: Can now generate UUIDv4-identifiers.
  • CHANGE: MediaBrowser: Single-clicks on thumbnails longer access items - double-clicking works somewhat as expected. Images can be opened in fullscreen by clicking the large image.
  • CHANGE: Fullscreen view: Clicking on the image now exits fullscreen instead of opening it in new tab. Middle click can be used to achieve the latter.
  • Developed on Chromium 142.0.7444.59, tested on Chromium 144.0.7559.96
  • TXID: OP3Y8FYjrlSZPOI4kU3SAnp822fgJvQcFmxmrk8-jTQ

0.6.4-ALPHA-WIP

  • NEW: The file manager is starting to be usable.
  • NEW: ArNS-resolving functionality added to the Util-section.
  • NEW: The 'block' variable (minimum and maximum block height) can now be set for GraphQL-queries.
  • NEW: Distinct values can now be sorted by the count - this behavior can be toggled with a setting in table options ('AUTO' sorts by count if extra info is enabled).
  • NEW: Initial version of transaction-categorizing added (column 'Category')
  • FIX: Distinct value resolving improved.
  • NEW: A column containing a "VIEW"-button added to transaction listings.
  • TXID: mRBR20r639y0EAXRhmllikKEOsgS1CwxuIO0sUpBvRs

0.6.3-ALPHA

  • SECURITY: Integrity of the scripts is now verified on load (by the browser using the 'integrity' attribute) - this is only relevant for the upload-section for now.
  • BUGFIX: Number columns should no longer cause a crash if the value is a string.
  • NEW: CONFIG: Key 'Enable integrity-check for loaded scripts' added.
  • FIX: Checks for non-OK status added to (some) fetches.
  • FIX: One of the 'App-Name' entries for the PermaButler tag template fixed (was 'permabutler', should have been 'Permabutler').
  • FIX: Tables now reset to the first page when filters are applied.
  • CHANGE: Arweave-JS is now initialized using the active gateway URL (unless the config key 'ArweaveJS_UseDefaultOpts' is set to false).
  • CHANGE: The Upload-section (that is still highly experimental) overhauled.
  • TXID: BxBZTzpTYWQJAAuMKx2K0Zq1eMJxOf2316U881Ecsio

0.6.2-ALPHA

  • NEW: STARGRID: Player search-feature added to the player activity section; this also resolves the session-addresses used by those logging onto the game with an Ethereum-wallet (Metamask) - however, StarGrid currently fails to save the turn-summaries of these players, so only activity is available.
  • BUGFIX: DATA-TABLES: Distinct values should now be properly resolved for columns that have object-values.
  • BUGFIX: QUERY: The transaction-tags in the Query-section should now behave correctly when an upper entry is removed.
  • BUGFIX: The datalog for network price is now created properly, and the fetch time is saved as was intended.
  • CHANGE: The fault-state indicator (at bottomleft) now animates.
  • CHANGE: Moved the OPTIONS-button to the right.
  • CHANGE: DATA-TABLES: Extra info is now enabled by default.
  • CHANGE: QUERY: Added some new data displays to the config-table and arranged things a bit while at it.
  • CHANGE: ABOUT: Addresses-section added.
  • CHANGE: STARGRID: The fetch-sequence status indicator now shows ERROR if the relevant query failed.

0.6.1-ALPHA

  • FIX: Adding a new gateway with the dropdown-menu now also adds it to the GatewayList-setting.
  • FIX: Gateways in the GatewayList-setting are now added to the dropdown-menu (which is no longer pre-filled).
    Considered adding a fallback-list if the menu was empty after init, but felt that the target userbase
    is advanced enough to add a gateway in this instance and opted to maintain a 1:1 relation between the menu and the setting.
  • FIX: StarGrid: The player activity-table is now properly displayed.
  • FIX: The retry-message of GraphQL-query no longer shows a null-prefix.
  • FIX: Adding a gateway from the Options-section now sanitizes it like adding it from the dropdown-menu does.
    This behavior can be disabled with the setting/hash-argument 'ExactGWURL'
  • CHANGE: If the active gateway is not present in the GatewayList-setting, it is set to the first item of the aforementioned setting.
    This can occur when removing a gateway that was in use and is a safety measure to ensure that removed gateways will not be used.
    Might add further safeguards regarding this as well.
  • CHANGE: The Owners-field in Transactions is now clear by default (was my address).
  • CHANGE: Gateways arweave.dev and ar.xyz removed from the defaults, arnode.xyz added.

0.6.0-ALPHA

  • NEW: Converters added to the Util-section
  • NEW: Table data can now be filtered.
  • NEW: Loglevels implemented. Also able to log into IndexedDB.
  • NEW: Errors (and other messages) can now be acknowledged.
  • NEW: Options are now saved to IndexedDB.
  • NEW: StarGrid data/replay viewer added - still heavily a work in progress
  • CHANGE: Rewrote the UI-portion of the data-tables.
  • CHANGE: Swapped the background-color of active and disabled input elements (active is now black, inactive gray).
  • CHANGE: IndexedDB-database 'DataLog' renamed to 'SART_DataLog' to lower chances of clashes in the same origin.
    ('file://' appears to be shared at least in Chrome).
  • VISUAL: Mouseover on buttons now animates.

Settings

Manage
Print to console
Save to
Set to
Security

NOTE: Changes will NOT be applied to HTML-elements that already exist.

About

Minimum safe block distance for conflict-resolution is used to resolve clashes such as multiple ArFS-drives created with the same Drive-Id. If the conflicting metadata is mined at least this many blocks after the first metadata using the conflicting ID, the first transaction will be considered as the owner of the node/drive.

If the distance is smaller than this, SART disables the item as unsafe to use. The disabled nodes can still be accesses via "By address" if the user knows the address the item should belong to.

Do NOT lower this value unless you absolutely know what you're doing.

Note that setting this to zero or no value will still disable nodes if the metadata-transactions competiting for the ownership are in the same block, as the order in which the transactions appear in this case is arbitrary and cannot be used to determine the owner.

Gateways
System
bytes
Network parameters
Links , , and
Data display
File Manager
Behavior
Autoscroll
Media viewer
Timeshift
Application log
Loglevels
Autofetch and datalogging
Data Autofetch Interval Logging Export
MemPool sec
Network info sec
Network price sec
Mempool-log: -
GraphQL

TRANSACTION QUERY TEMPLATE

NOTE: Changes are applied only to queries that are created after the modification and will NOT persist after page reload.

Set to TEMPLATE NOT DEFAULT
Substituting
About

The following keywords will get substituted within GraphQL-queries:

%%VARDEFS%%Replaced by definitions for query-variables that are present, e.g '$ids: [ID!], $owners: [String!]'
%%TXVARS%%Replaced by parameters of TransactionConnection for query-variables that are present, e.g 'ids: $ids, owners: $owners'
%%BUNDLE_DEF%%Replaced by '$bundledIn: [ID!]' if bundledIn is present in the query-variables or with empty string ("") if it isn't. Does not currently obey any of the substitution-settings.
%%BUNDLE_VAR%%Replaced by 'bundledIn: $bundledIn' if bundledIn is present in the query-variables or with empty string ("") if it isn't. Same as above.

The query-template 'Dynamic variables' makes use of these keywords. By default, variables that are null or empty will also be included - the settings above control this behavior. Not including variables that are null or empty arrays may improve query performance, but may result in incorrect results when these arguments are desired (e.g. when wanting to query for transactions that aren't in a bundle).

Test not ran.

Upload

Read this first

WARNING

Data uploaded with this utility will be PERMANENTLY ACCESSIBLE BY EVERYONE and IT CANNOT EVER BE DELETED OR ALTERED, so be absolutely certain that it does NOT contain any sensitive information or anything you might regret later on in life. The data will be stored into Arweave, a data-preservation blockchain designed to archive tamper-proof data for hundreds of years.

arweave-js
StateNOT LOADED
Source-
Controls
Key control
> Wallet-extension - <
> Loaded key - < Not loaded
New transaction

TAGS

NameValue

DATA

TypeSourceSizeChunk-alignModified
Updated on -

TRANSACTION

Owner -
Recipient
Quantity
Bundler -
Method
Directly to network Using bundler
Balance
Balance after
TX fee
SART fee
Total cost
Execute
OR
Wasted
Manual control

Posted transactions
as

Network status

Fetch price

Transactions

IDs
Owners
Recipients
Bundled in
Tags
Block
First
Sort
After
New query or fetch
State
StatusTime startedLatest fetchRequestsPagesFailedEdgeshasNextPage
NOT STARTED
Cursor
Errors
-
Continue or fetch
Control

!!! NOT PRODUCTION-READY - CONVERSIONS MAY BE INACCURATE !!!

Time UnixTime (sec): UnixTime (ms): Block height:
Value converter
FROM
TO
Generating values UUIDv4:
ArNS

or

Request time URL ArNS-name Status Resolved TXID TTL (sec) PID Resolved at

Testing

StarGrid

Disclaimer

This feature is still heavily experimental and may provide incorrect or incomplete data.
SART is not affiliated with StarGrid.

Player Activity

This utility can retrieve game turns, game moves and/or control-actions (queuing etc.)
using the given Arweave-addresses. These can be manually added (can use the 'ArweaveId' column of the Leaderboard) or obtained with the "Search for players"-feature.

StarGrid is currently not storing the turn-results of players who use MetaMask or compatible Ethereum-wallet
to play the game, and as such, this utility can't for now display the turns of these players.

I recommend using Wander to log onto the game until this issue is fixed.

I may one day seek to reconstruct these missing turns by re-executing the game process
from player inputs (which are stored), but that day is not today.

Search for players

Player data: Not fetched

Retrieve player data

From Arweave-addresses
or
Setup
Fetch or data-items

Control activity 0
Game activity 0
Player turns 0
Other turns 0
Turn data 0

Retrieved data

Player turns

Turn details

Objects

Actions