Gopulse
Gopulse portfolio: first address lookup and device sync in the legacy tracker
Gopulse portfolio tracked address holdings within the PulseChain suite, using local records and optional device synchronization through a portfolio ID. The original suite later reported a June 1 shutdown, without naming a year. Its legacy design kept portfolio data on the entry device unless the user enabled sharing. Possession of the ID allowed portfolio viewing and editing, while wallet spending authority remained separate.
Address lookup, custom balance records, and synchronization served different purposes. An address identified holdings for inspection, while the portfolio ID granted access to a saved collection. Custom balances were user-entered portfolio records.
The legacy portfolio ID allowed viewing and editing of a saved address collection without granting authority to spend wallet funds.
Inspect an address in the former tracker
Address lookup was a way to inspect holdings associated with an address through the legacy portfolio interface. The reader opened a fresh incognito tab, opened the portfolio, entered an address, and pressed Enter. An address lookup did not require device synchronization.
Local addresses, assets, and custom balances
The legacy tracker kept addresses, assets, and custom balances on the entry device by default. The local arrangement explained why a collection entered on one device did not automatically appear on another. Synchronization changed that arrangement through an explicit sharing choice.
The local-storage default applied to portfolio records. Revealing the synchronization ID allowed those records to leave the device, including the collection of addresses.
What access did a portfolio ID grant?
An 8-digit portfolio ID granted its holder viewing and editing access to the linked portfolio. Sharing it exposed the saved collection, including which addresses appeared together. The ID therefore carried a privacy risk even when the constituent addresses could be looked up separately.
Wallet spending authority remained outside the ID’s permissions. Someone holding the ID could change tracker information without gaining the ability to spend the associated funds.
Enable device synchronization in the former tracker
The legacy synchronization sequence linked a saved portfolio to other devices through its existing ID. The original interface exposed the controls in this order: “Edit”, “Export”, then “Reveal my GoPulse ID”. Revealing the ID allowed locally stored portfolio data to leave the device. The ID’s viewing and editing permissions also applied to access from those other devices.
An additional device used “Login with GoPulse ID”, followed by entry of the copied identifier. This connected it to the existing portfolio and enabled automatic synchronization between devices. GoPulseX handled token swaps in a separate interface; portfolio synchronization did not exchange assets between devices.
An address inspection and a shared collection
In a hypothetical first session in the former interface, a reader had an illustrative address, a locally saved portfolio with an unrevealed ID, and an additional device. Would inspecting the address also share the collection?
The original design kept locally entered portfolio records on the entry device by default. An address supplied a lookup input, while the portfolio ID supplied access to a saved collection.
The reader opened a fresh incognito tab, opened the portfolio, entered the illustrative address, and pressed Enter. The resulting holdings view concerned that address. It did not establish access to the saved collection on the additional device.
The reader could share the saved collection by revealing and copying its portfolio ID, then entering it through “Login with GoPulse ID” on the additional device. This would give the device access to the saved portfolio.
Any holder of the shared ID could then view and edit the portfolio without gaining authority to spend wallet funds. After viewing the address’s holdings, the reader could stop without revealing the portfolio ID or enabling device synchronization.
Custom balance records and asset quantities
Custom balances belonged to the tracker’s locally entered data, alongside its address and asset records. Editing that information changed the tracker record, while wallet credentials controlled spending of the associated funds. A recorded amount needed its asset and unit to make sense as a balance.
An asset quantity and a monetary valuation used different units. The quantity counted units of the asset; its monetary value required a corresponding price. Editing a custom balance did not itself move assets between addresses or establish a current wallet balance.
The limit of portfolio-based address inspection
The portfolio lookup served as a temporary address-inspection tool in the legacy interface. A fuller explorer appeared as a possible expansion in its help material. That proposal belonged to the old design discussion and did not establish additional explorer functions as available through the portfolio lookup.
Portfolio access after the shutdown
The original Gopulse suite announced a June 1 shutdown without specifying the year. The address-entry and device-login instructions described the former interface. Recovery through the old portfolio ID remained uncertain after the shutdown.
Everyday questions about Gopulse portfolio
Could an ENS name replace a raw address in the legacy portfolio input?
The legacy portfolio lookup accepted an ENS name as an alternative to a raw address. The name belonged in the address lookup input, followed by Enter. This support concerned that specific lookup feature; it did not make an ENS name a substitute for the portfolio ID used for synchronization.
Did possessing a portfolio ID prove ownership of the tracked addresses?
Possessing a portfolio ID did not prove control of the addresses in its saved collection. Anyone holding the ID could view and edit that portfolio.
How much did the former Gopulse suite charge for portfolio access?
The former suite provided free access to its portfolio tool. It did not establish a currently available portfolio service or a price for restoring records after the original suite shut down.
Was account registration required for a first legacy portfolio lookup?
The former suite did not require account registration. Optional cross-device access used the existing portfolio ID through the synchronization login. The presence of a login control referred to accessing portfolio records; it did not establish a new wallet account or confer spending authority over the addresses being tracked.
Was the legacy Export option a way to obtain a portfolio backup file?
The legacy Export flow led to revealing the portfolio ID for device synchronization. Whether the tracker also offered a separate downloadable backup file remains unconfirmed. The identifier provided access to the saved collection in the former service; it was not itself a backup file.
Last updated -