[{"data":1,"prerenderedAt":708},["ShallowReactive",2],{"news-article:en:\u002Fnews\u002Fpulse\u002Fpulse-release-1.0.0-alpha4":3,"related-news:en:\u002Fnews\u002Fpulse\u002Fpulse-release-1.0.0-alpha4":250},{"id":4,"title":5,"body":6,"description":235,"extension":236,"meta":237,"navigation":245,"path":246,"seo":247,"stem":248,"__hash__":249},"content_en\u002Fnews\u002Fpulse\u002Fpulse-release-1.0.0-alpha4.md","HashCore Pulse 1.0.0-alpha4: from a single operator to a whole team",{"type":7,"value":8,"toc":222},"minimark",[9,14,21,58,74,118,130,146,162,184,193,219],[10,11,13],"h1",{"id":12},"hashcore-pulse-100-alpha4","HashCore Pulse 1.0.0-alpha4",[15,16,17],"blockquote",{},[18,19,20],"p",{},"The first Pulse releases were about helping one person handle a large fleet: see everything in one window, act in bulk, automate the routine. But a large farm is never just one person. It is the owner, managers, on-site technicians, and sometimes hosting clients who need to see their own devices. Alpha4 is the release where Pulse starts working for the whole team.",[22,23,24,29,41,44,47],"section",{},[25,26,28],"h2",{"id":27},"personal-or-business-a-workspace-that-fits-your-scale","Personal or Business: a workspace that fits your scale",[18,30,31,32,36,37,40],{},"On first sign-in, Pulse asks how you work. ",[33,34,35],"strong",{},"Personal"," is for your own farm, when you run everything yourself. ",[33,38,39],{},"Business"," is for a company where a team works with the fleet.",[18,42,43],{},"Until the stable release, both plans are free and work without limits — the choice is about how your work is organized, not about price.",[18,45,46],{},"The decision is not final: you can switch both ways. When moving from Business back to Personal, Pulse does not silently delete anything — the owner picks one site that keeps all its data and sees exactly what will be removed before confirming.",[18,48,49,50,53,54,57],{},"Navigation is now split into two levels: ",[33,51,52],{},"Account"," for your personal settings and ",[33,55,56],{},"Organization"," for managing the company. Existing accounts have been migrated automatically, so there is nothing to set up again.",[22,59,60,64,71],{},[25,61,63],{"id":62},"the-whole-team-in-one-workspace","The whole team in one workspace",[18,65,66,67,70],{},"Business plans get a new ",[33,68,69],{},"Members"," section. Invitations are sent by email, all members are visible in one list, and access can be blocked or removed. Members are notified when their status changes — nobody discovers they lost access by accident while trying to sign in.",[18,72,73],{},"Until now, shared access to a farm usually meant one shared login for everyone. That is inconvenient and unsafe: there is no way to tell who did what, and no way to revoke one person's access without changing the password for everyone else. Now every member has their own account in the organization.",[22,75,76,80,83,115],{},[25,77,79],{"id":78},"five-roles-for-real-responsibilities","Five roles for real responsibilities",[18,81,82],{},"Roles in Pulse mirror how responsibilities are split on a real farm:",[84,85,86,97,103,109],"ul",{},[87,88,89,92,93,96],"li",{},[33,90,91],{},"Owner"," and ",[33,94,95],{},"Administrator"," manage everything — from devices to team membership.",[87,98,99,102],{},[33,100,101],{},"Operations Manager"," handles day-to-day device operations.",[87,104,105,108],{},[33,106,107],{},"Technician"," works on site but has no access to critical settings such as pools — an accidental edit will not send hashrate to someone else's pool.",[87,110,111,114],{},[33,112,113],{},"Viewer"," can see but not change anything — a good fit for hosting clients, investors and observers.",[18,116,117],{},"The role is chosen right in the invitation dialog, so a new member gets exactly the permissions they need from their very first sign-in.",[22,119,120,124,127],{},[25,121,123],{"id":122},"per-site-access-everyone-sees-their-own","Per-site access: everyone sees their own",[18,125,126],{},"The second half of the access model is sites. A member can be assigned to specific sites and will see only their devices, metrics and events. A technician on one site is not distracted by incidents elsewhere, and a hosting client sees only their own equipment.",[18,128,129],{},"Owner and Administrator see all sites, including ones added in the future — there is no need to grant management access to each new site separately. Like the role, sites are chosen in the invitation dialog.",[22,131,132,136,143],{},[25,133,135],{"id":134},"pool-presets-one-configuration-for-the-whole-fleet","Pool presets: one configuration for the whole fleet",[18,137,138,139,142],{},"Changing pools across a large fleet is a frequent and risky operation: one typo in an address or worker name, and part of the hashrate goes nowhere. Now a pool configuration — ",[33,140,141],{},"URL, Worker and Password in all three slots"," — can be saved as a named preset.",[18,144,145],{},"The preset is applied in Pools config to a single device or a whole group. Presets are shared across the organization and available on any site: set it up once, and the whole team uses one verified configuration instead of typing it in by hand.",[22,147,148,152,159],{},[25,149,151],{"id":150},"autoswitch-for-every-model","Autoswitch for every model",[18,153,154,155,158],{},"In Performance config, Exact mode, ",[33,156,157],{},"Autoswitch"," is now configured separately for each model. On a mixed fleet this matters: behavior that suits one model does not necessarily suit another.",[18,160,161],{},"When a model is switched to manual overclocking, Autoswitch is turned off for it automatically — the settings never conflict, and there is no need to remember to disable it by hand.",[22,163,164,168,174],{},[25,165,167],{"id":166},"avalon-braiins-and-auradine","Avalon, Braiins and Auradine",[18,169,170,173],{},[33,171,172],{},"Canaan Avalon"," devices are now monitored on par with everything else. Reboot, pool changes and Find Miner work the same way as for HashCore Firmware, Bitmain and WhatsMiner — without opening each device's web interface separately.",[18,175,176,177,92,180,183],{},"Support for ",[33,178,179],{},"Braiins",[33,181,182],{},"Auradine"," devices has also been added. The more manufacturers Pulse covers, the less equipment on a mixed fleet has to be managed separately.",[22,185,186,190],{},[25,187,189],{"id":188},"stability-you-do-not-have-to-watch","Stability you do not have to watch",[18,191,192],{},"If the service is temporarily unavailable, Pulse opens a status page instead of a confusing error. Pulse checks for recovery on its own and brings you back to work without a manual page refresh.",[22,194,195,199,202,205,208],{},[25,196,198],{"id":197},"summary","Summary",[18,200,201],{},"Alpha4 turns Pulse from a single operator's tool into a team workspace: every member has their own account, role and sites, while shared settings such as pool presets work across the whole organization.",[18,203,204],{},"Pulse is in alpha — we are building the platform together with the people who use it. Already in development: new HashCore firmware with a built-in Pulse agent, device grouping, email and Telegram alerts, an issue tracker and reports.",[18,206,207],{},"Join, invite your team and send us feedback — it directly shapes what goes into the next release.",[18,209,210],{},[33,211,212,213],{},"Register: ",[214,215,216],"a",{"href":216,"rel":217},"https:\u002F\u002Fhashcore.com\u002Fpulse",[218],"nofollow",[220,221],"article-signature",{},{"title":223,"searchDepth":224,"depth":224,"links":225},"",2,[226,227,228,229,230,231,232,233,234],{"id":27,"depth":224,"text":28},{"id":62,"depth":224,"text":63},{"id":78,"depth":224,"text":79},{"id":122,"depth":224,"text":123},{"id":134,"depth":224,"text":135},{"id":150,"depth":224,"text":151},{"id":166,"depth":224,"text":167},{"id":188,"depth":224,"text":189},{"id":197,"depth":224,"text":198},"Organizations with roles and per-site access, pool presets for the whole fleet, and support for Avalon, Braiins and Auradine — Pulse becomes a tool for the entire team.","md",{"img":238,"date":239,"dateISO":240,"tags":241,"slug":244},"\u002Fimages\u002Fnews\u002Fpulse-news.png","12 Oct 2026","2026-10-12",[242,243],"pulse","release","pulse\u002Fpulse-release-1.0.0-alpha4",true,"\u002Fnews\u002Fpulse\u002Fpulse-release-1.0.0-alpha4",{"title":5,"description":235},"news\u002Fpulse\u002Fpulse-release-1.0.0-alpha4","3vYvhbFDrpRi6ZzjJ3INDGG1ftmcPLe7gXUZTHAEJGQ",[251,514],{"id":252,"title":253,"body":254,"description":504,"extension":236,"meta":505,"navigation":245,"path":510,"seo":511,"stem":512,"__hash__":513},"content_en\u002Fnews\u002Fpulse\u002Fpulse-release-1.0.0-alpha3.md","HashCore Pulse 1.0.0-alpha3: the platform learns to act on its own",{"type":7,"value":255,"toc":495},[256,260,265,305,372,388,432,457,473,493],[10,257,259],{"id":258},"hashcore-pulse-100-alpha3","HashCore Pulse 1.0.0-alpha3",[15,261,262],{},[18,263,264],{},"The first Pulse release answered the question \"what is happening with my fleet right now.\" The next two — alpha2 and alpha3 — answer a different one: \"what should happen automatically, without me.\" The difference is fundamental, and it defines everything in these two releases.",[22,266,267,271,278,284,291,294],{},[25,268,270],{"id":269},"automation-rules-instead-of-calendar-reminders","Automation: rules instead of calendar reminders",[18,272,273,274,277],{},"Previously, routine operations — a nightly fleet restart, pool switching on schedule — depended on a person being in the right place at the right time. Missed the moment, forgot, was busy with another incident — the operation didn't happen. The new ",[33,275,276],{},"Automation"," section removes this dependency entirely.",[18,279,280,283],{},[33,281,282],{},"Scheduled rules"," are the simple part: you choose the scope (specific models, the whole site, a scan task), set a time and action — and Pulse executes it automatically, once or on a recurring basis.",[18,285,286,287,290],{},"More interesting are ",[33,288,289],{},"conditional rules",". Here the value is not time savings but reaction speed. Pulse watches device state in real time and responds to deviations: status goes to Error, temperature exceeds a threshold, hashrate efficiency drops, fans hit their limit. A condition must persist for a set duration before triggering (to avoid reacting to brief spikes), and a per-device cooldown controls how often the action can repeat.",[18,292,293],{},"The difference between \"restart a hung miner an hour later when the operator finally notices during rounds\" and \"restart at the moment the problem occurs\" is the difference between lost and saved hashrate. On a large farm, that's hundreds of kilowatt-hours per month.",[18,295,296,301],{},[297,298],"img",{"alt":299,"src":300},"Pulse Automation Section","\u002Fimages\u002Fnews\u002Fpulse\u002Fpulse-release-1.0.0-alpha3\u002Fautomation-rules.png",[302,303,304],"em",{},"Conditional automation rule builder with trigger and cooldown period settings",[22,306,307,311,318,338,341,356,363],{},[25,308,310],{"id":309},"performance-presets-managing-a-fleet-not-individual-devices","Performance presets: managing a fleet, not individual devices",[18,312,313,314,317],{},"Manually configuring overclocking on each device doesn't scale when you have ten thousand machines instead of ten. The new ",[33,315,316],{},"Performance config"," group operation solves this in three ways:",[84,319,320,326,332],{},[87,321,322,325],{},[33,323,324],{},"Exact"," — need a specific preset for a specific model? Set it once, applied to the entire selection of that model.",[87,327,328,331],{},[33,329,330],{},"Gradient"," — managing a mixed fleet and want to normalize it to a common load level (from Eco to Max) without dealing with each model separately.",[87,333,334,337],{},[33,335,336],{},"Relative"," — reacting to a situation and just want to shift current settings a few steps up or down, without thinking about which preset is currently active.",[18,339,340],{},"The firmware auto-switcher is configured in the same dialog — no need to go into each device's settings separately.",[18,342,343,344,347,348,351,352,355],{},"The operation supports ",[33,345,346],{},"filter conditions",". In alpha2 these were Status and Temperature; in alpha3 ",[33,349,350],{},"Hashrate Efficiency"," (ratio of actual hashrate to the ideal for the current preset) and ",[33,353,354],{},"Power"," (actual wall consumption) were added. The practical value: you can apply a more aggressive preset only to devices whose efficiency has already fallen below 90%, leaving healthy devices untouched — a targeted action instead of a blanket one.",[18,357,358,359,362],{},"The same condition block in alpha3 was also added to ",[33,360,361],{},"Thermal config"," group operations — reused logic, not reinvented.",[18,364,365,369],{},[297,366],{"alt":367,"src":368},"Bulk Performance Configuration Dialog","\u002Fimages\u002Fnews\u002Fpulse\u002Fpulse-release-1.0.0-alpha3\u002Fperformance-config.png",[302,370,371],{},"Bulk performance configuration dialog with conditional device filtering",[22,373,374,378,385],{},[25,375,377],{"id":376},"service-mode-precise-tracking-during-bulk-operations","Service Mode: precise tracking during bulk operations",[18,379,380,381,384],{},"When a group of devices is sent for maintenance (for example, an entire rack), each now gets its ",[33,382,383],{},"own independent session"," with its own ID, even if a single reason is specified for the whole group. The repair history of each specific device stays accurate and separable from its neighbors — critical for operators who track maintenance per unit, especially in a hosting model where that history is shown to clients.",[18,386,387],{},"Mixed-selection handling was also fixed: if some selected devices are already in service mode and others are not, the operation now handles each group correctly instead of throwing an error or skipping the whole operation.",[22,389,390,394,400,413,426],{},[25,391,393],{"id":392},"less-repetitive-work-in-the-interface","Less repetitive work in the interface",[18,395,396,399],{},[33,397,398],{},"Filter Presets"," — if you open the same set of filters every day (\"workers of this model with errors,\" \"non-standard firmware on the site\"), you had to rebuild that combination from scratch on every login. Now it saves as a named preset and can be recalled in one click. Presets are shared within a site — set it up once, available to the whole team.",[18,401,402,405,406,410],{},[33,403,404],{},"Data export"," — the device list exports to CSV or XLSX directly from the interface, with column selection and ordering, generated server-side regardless of table pagination. This closes a workflow that was previously done manually and opens something that didn't exist before: sending hosting client data in a clean tabular format.\n",[297,407],{"alt":408,"src":409},"Device list data export","\u002Fimages\u002Fnews\u002Fpulse\u002Fpulse-release-1.0.0-alpha3\u002Fexport-data.png",[302,411,412],{},"Exporting device list in CSV or XLSX format with column customization",[18,414,415,418,419,423],{},[33,416,417],{},"Serial numbers"," in Custom mode and in export — two types of data at once: the control board serial number and the serial numbers of each hash board (Board 1\u002F2\u002F3 S\u002FN). Previously this data was only visible one device at a time. Now it can be shown as columns across the entire fleet — which directly solves a painful scenario: cross-referencing serial numbers for a warranty claim against a supplier, without opening each device's card individually.\n",[297,420],{"alt":421,"src":422},"Serial numbers and filter presets in table","\u002Fimages\u002Fnews\u002Fpulse\u002Fpulse-release-1.0.0-alpha3\u002Fcustom-columns-sn.png",[302,424,425],{},"Hash board serial numbers display in the device table and quick loading of saved filter presets",[18,427,428,431],{},[33,429,430],{},"Bulk note management"," — assign or clear a note on multiple selected devices in one operation instead of opening each device separately. Small in effort, but exactly these small things accumulate into meaningful daily overhead on a fleet of thousands.",[22,433,434,438,445,448],{},[25,435,437],{"id":436},"devfee-transparency-where-guesswork-used-to-be-required","DevFee: transparency where guesswork used to be required",[18,439,440,441,444],{},"A fourth pool card — ",[33,442,443],{},"DevFee"," — now appears in the device card. A portion of any device's hashrate goes to the firmware developer fee — this is normal and required for operation, but it was previously invisible in the interface. Users would periodically write to support asking \"where did part of my power go\" or \"why doesn't the statistics add up.\"",[18,446,447],{},"Now the stats for this system pool are visible separately, using the same familiar visual language as the working pools — the question is answered with a glance at the card, not a support ticket.",[18,449,450,454],{},[297,451],{"alt":452,"src":453},"DevFee Pool Card in Device Details","\u002Fimages\u002Fnews\u002Fpulse\u002Fpulse-release-1.0.0-alpha3\u002Fdevfee-pool-card.png",[302,455,456],{},"Separate DevFee system pool card in device details",[22,458,459,463,466],{},[25,460,462],{"id":461},"whatsminer-from-observation-to-full-control","WhatsMiner: from observation to full control",[18,464,465],{},"MicroBT devices were visible in Pulse from the start — monitoring worked. But direct control wasn't possible: you had to open the web interface of each miner separately, losing the whole point of a centralized platform.",[18,467,468,469,472],{},"Now the basic operations — ",[33,470,471],{},"Pause, Resume, Reboot, password change, pool switching"," — work for WhatsMiner via the vendor's native API, the same way they work for HashCore Firmware and Bitmain. For operators with a mixed fleet (which is most of the market), this eliminates the awkward reality where part of the equipment is managed from a single interface and part requires a separate login.",[22,474,475,477,480,483,486],{},[25,476,198],{"id":197},[18,478,479],{},"Both releases share one logic: remove from the operator's workflow what can and should happen automatically or in bulk, without sacrificing control or tracking accuracy. Every action remains visible in the Activity Center with a full history, and data for each device — including maintenance records and serial numbers — stays accurate even during bulk operations.",[18,481,482],{},"Pulse is in alpha — we're building the platform together with those who work on it. Currently in development: pool presets, device grouping, a technical issue tracker, roles and access rights, reports, email and Telegram alerts, and embedding the agent directly into HashCore firmware.",[18,484,485],{},"Join, test features on your farm, and send feedback — it directly shapes what goes into the next release.",[18,487,488],{},[33,489,212,490],{},[214,491,216],{"href":216,"rel":492},[218],[220,494],{},{"title":223,"searchDepth":224,"depth":224,"links":496},[497,498,499,500,501,502,503],{"id":269,"depth":224,"text":270},{"id":309,"depth":224,"text":310},{"id":376,"depth":224,"text":377},{"id":392,"depth":224,"text":393},{"id":436,"depth":224,"text":437},{"id":461,"depth":224,"text":462},{"id":197,"depth":224,"text":198},"Scheduled and conditional automation, fleet-wide performance presets, full WhatsMiner control, and dozens of interface improvements across two new HashCore Pulse releases.",{"img":238,"date":506,"dateISO":507,"tags":508,"slug":509},"13 Aug 2026","2026-08-13",[242,243],"pulse\u002Fpulse-release-1.0.0-alpha3","\u002Fnews\u002Fpulse\u002Fpulse-release-1.0.0-alpha3",{"title":253,"description":504},"news\u002Fpulse\u002Fpulse-release-1.0.0-alpha3","sC6qN8LhUNDDYU2a2gQS5NyIMuOMCzb3MfnBTWQG42M",{"id":515,"title":516,"body":517,"description":698,"extension":236,"meta":699,"navigation":245,"path":704,"seo":705,"stem":706,"__hash__":707},"content_en\u002Fnews\u002Fpulse\u002Fpulse-release-1.0.0-alpha1.md","HashCore Pulse 1.0.0-alpha1: a mining farm management platform built together with operators",{"type":7,"value":518,"toc":686},[519,523,526,533,545,557,579,595,618,630,639,651,660,684],[10,520,522],{"id":521},"hashcore-pulse-100-alpha1","HashCore Pulse 1.0.0-alpha1",[18,524,525],{},"When a fleet of a thousand ASICs is scattered across multiple locations, the most common problem is not a lack of data, but too much of it without context. Everyone has metrics: hash rate, temperature, consumption—any tool that can query a miner's API can read that. The difference begins where the table of numbers ends: in whether the system distinguishes scheduled maintenance from failures, allows for safe simultaneous restarts of five thousand devices, and speaks the language of the operator, not just the exchange.",[18,527,528,529,532],{},"HashCore Pulse is a cloud platform for monitoring and managing industrial ASIC fleets, designed to scale from a single rack to hundreds of thousands of devices across multiple sites. In July 2026, we released the first version—",[33,530,531],{},"1.0.0-alpha1","—and here we explain what went into it and why this is only the beginning.",[22,534,535,539,542],{},[25,536,538],{"id":537},"an-ecosystem-not-just-a-standalone-product","An ecosystem, not just a standalone product",[18,540,541],{},"Pulse is not our first development. HashCore has been creating its own firmware for ASIC devices for several years (HashCore Firmware), the HashCore Toolkit desktop application, and the free HashCore Proxy Stratum proxy. Pulse is the fourth product in the ecosystem, and in the future, some of the Proxy functionality will be integrated directly into the platform itself.",[18,543,544],{},"Today, Pulse manages Bitmain and MicroBT (WhatsMiner) hardware running Stock and HashCore firmware. Separately, without active control, the platform also displays statistics from devices running Braiins, Luxor, and ePIC firmware—meaning that even a fleet with mixed firmware is visible in one place, even if not all of it can be managed yet.",[22,546,547,551,554],{},[25,548,550],{"id":549},"devices-are-discovered-automaticallyno-manual-addition-needed","Devices are discovered automatically—no manual addition needed",[18,552,553],{},"Each site (farm location) is configured separately: its own electricity tariff, power limit, and display currency for financial indicators. At the same time, equipment is not added manually—the agent on the farm server scans the specified IP ranges, discovers the devices itself, and then simply collects metrics from them.",[18,555,556],{},"If the farm previously ran on a different system, migration does not require rebuilding the equipment list from scratch: Pulse can import network ranges from HashCore Toolkit, Hive OS, Awesome Miner, and Bitcap. And if the scanning task (ScanTask) is later deleted, all associated devices are completely removed from the system—rather than hanging in an Offline status.",[22,558,559,563,566,576],{},[25,560,562],{"id":561},"offline-failure","Offline ≠ failure",[18,564,565],{},"In most monitoring systems, device status is a single field. In Pulse, there are two, and they are independent of each other.",[18,567,568,571,572,575],{},[33,569,570],{},"Connectivity"," is solely responsible for whether there is communication with the device. ",[33,573,574],{},"Miner Status"," is responsible for what it is physically doing: mining, stopped, undergoing autotuning, or in error. If power was lost on a rack at night, that is indeed Offline, and an alert should trigger. But if a miner is simply paused while remaining healthy and online, that is a different state, and a redundant alert is not needed.",[18,577,578],{},"It sounds like a small detail, but it is precisely because of the confusion of these two concepts in competing systems that real failures often drown in dozens of planned stops per shift.",[22,580,581,585,592],{},[25,582,584],{"id":583},"maintenance-is-not-an-incident","Maintenance is not an incident",[18,586,587,588,591],{},"An extension of the same concept is the ",[33,589,590],{},"Service mode",". When a technician removes a device from a rack for repair, it is set to a separate status specifying the reason for the downtime. While the device is in service, it is excluded from error statistics and automatically skipped during group operations—with a clear notification of how many devices were excluded and why.",[18,593,594],{},"A separate history is saved for each service session: when it started, what was done, how long it took, and who was responsible. Both a single device and an entire rack can be put into this mode in a single operation. For operators managing client equipment, this is especially valuable: the service log becomes a transparent document rather than a set of red dots in a general log of failures.",[22,596,597,601,604,607],{},[25,598,600],{"id":599},"see-what-is-needed-now-not-just-a-table","See what is needed now, not just a table",[18,602,603],{},"A list of thousands of devices is useless if you have to scroll through cards one by one for every check. In Pulse, the table can be instantly switched to a mode displaying the configuration of each device's pools: which pool is currently active and how the others are configured. There is no need to open each device separately to find those with drifted pool settings.",[18,605,606],{},"Columns for sorting are grouped logically—hash rate, temperatures, network, firmware—instead of a flat list of twenty unrelated fields. The event log for each device records changes in a \"before → after\" format: if someone changed the overclocking preset a week ago, the exact values before and after are visible, rather than an abstract \"settings changed\" entry.",[18,608,609,610,613,614,617],{},"A specific feature for those physically working with racks: the ",[33,611,612],{},"IP Report"," button on the ASIC device itself allows technical staff to immediately identify a specific machine in the interface—press on the chassis, and the device appears in a separate list in Pulse. It also works in reverse: the ",[33,615,616],{},"Locate"," command helps find the required device physically among hundreds of similar ones on a rack.",[22,619,620,624,627],{},[25,621,623],{"id":622},"bulk-operations-that-dont-crash-the-grid","Bulk operations that don't crash the grid",[18,625,626],{},"Reboot, change pools, update firmware, manage hash boards and cooling—any operation can be applied to either a single device or an arbitrary group. However, a command to five thousand devices is not sent in a single burst: Pulse staggers it in batches with a configurable delay between them, so that a simultaneous restart of the entire fleet does not create a peak load on the site's power grid.",[18,628,629],{},"Once the operation is complete, the exact success percentage is shown, and if some devices failed to execute the command, they can be isolated with a single click without reviewing the entire list manually. Group management of hash boards and cooling additionally supports conditional logic—for example, disabling a specific board if it is in an error state or a temperature threshold is exceeded—and partial updates, where empty fields do not affect the device's current settings.",[22,631,632,636],{},[25,633,635],{"id":634},"comparison-with-rated-performance","Comparison with rated performance",[18,637,638],{},"In addition to the current and average daily hash rate, the device card displays the factory (stock) rate—a reference point for comparison. If a batch of equipment falls short of the declared characteristics, it is not a vague feeling of \"seems to run hotter,\" but a specific percentage of the rated power that can be presented to the supplier.",[22,640,641,645,648],{},[25,642,644],{"id":643},"finance-in-the-operators-language","Finance in the operator's language",[18,646,647],{},"Site profitability is calculated not only in dollars but also in the mined coin—for many operators, this is more important than the exchange rate on a specific day. The Bitcoin and Litecoin exchange rates are visible right on the dashboard, without switching to an exchange website.",[18,649,650],{},"For operators outside the US, site financial indicators—revenue, electricity costs, analytics—can be fully translated into rubles, euros, yuan, or tenge. Among Western competitors strictly tied to the dollar model, this is a rarity.",[22,652,653,657],{},[25,654,656],{"id":655},"account-protected-at-a-level-familiar-to-enterprise","Account protected at a level familiar to enterprise",[18,658,659],{},"Two-factor authentication, a list of active sessions with the ability to terminate any of them remotely, password reset, and account deletion in accordance with GDPR—a basic set of features that in this segment often turns out to be missing rather than basic.",[22,661,662,666,669,672,675],{},[25,663,665],{"id":664},"where-we-are-now","Where we are now",[18,667,668],{},"Pulse is in alpha—we are launching the platform early on purpose to build it together with those who will use it. New releases come out regularly, and what goes into the next one is largely determined by feedback from real operators.",[18,670,671],{},"Currently in development: pool and filter presets, group management of device presets, scheduled automation and conditional triggers, exporting data from the device table, user grouping of devices, technical issue tracker, roles and access permissions, reports, email and Telegram notifications, and embedding the agent directly into the HashCore firmware so that device discovery works out of the box without a separate installation.",[18,673,674],{},"Connect, test the features on your farm, and send feedback—it directly affects what goes into the next release.",[18,676,677],{},[33,678,679,680],{},"Registration: ",[214,681,682],{"href":682,"rel":683},"https:\u002F\u002Fpulse.hashcore.com\u002Fauth\u002Fregister",[218],[220,685],{},{"title":223,"searchDepth":224,"depth":224,"links":687},[688,689,690,691,692,693,694,695,696,697],{"id":537,"depth":224,"text":538},{"id":549,"depth":224,"text":550},{"id":561,"depth":224,"text":562},{"id":583,"depth":224,"text":584},{"id":599,"depth":224,"text":600},{"id":622,"depth":224,"text":623},{"id":634,"depth":224,"text":635},{"id":643,"depth":224,"text":644},{"id":655,"depth":224,"text":656},{"id":664,"depth":224,"text":665},"Cloud platform HashCore Pulse 1.0.0-alpha1 for monitoring and managing industrial ASIC fleet. Distinguishes scheduled maintenance from failures and scales up to hundreds of thousands of devices.",{"img":238,"date":700,"dateISO":701,"tags":702,"slug":703},"1 Jul 2026","2026-07-01",[242,243],"pulse\u002Fpulse-release-1.0.0-alpha1","\u002Fnews\u002Fpulse\u002Fpulse-release-1.0.0-alpha1",{"title":516,"description":698},"news\u002Fpulse\u002Fpulse-release-1.0.0-alpha1","dORoyLGGT2rR3uDQPQf72OLFh28zR1aMiRJ82sg7_Vc",1792440756701]