New Reward Pool: Uptime Starts Counting Tomorrow - November 1st
For those who elect to participate in the new reward pool - uptime starts counting approximately 8 hours from now at Midnight GMT.
Ensure that your visors are online, and you should see rewards starting on November 2nd.
The reward system is now funded and ready to distribute rewards for November.
For questions or technical assistance ---> @skywire <---
For those who elect to participate in the new reward pool - uptime starts counting approximately 8 hours from now at Midnight GMT.
Ensure that your visors are online, and you should see rewards starting on November 2nd.
The reward system is now funded and ready to distribute rewards for November.
For questions or technical assistance ---> @skywire <---
Minimum Version Requirement
The minimum version requirement for reward eligibility has been incremented to v1.3.28
The deadline for updating to v1.3.28 is February 1st 2025
Older versions will be ineligible for rewards after this time.
Most visors on the network are already running the requisite version
For rewards on windows, users must run either the latest commits to the develop branch or a release candidate for v1.3.29.
Network Statistics
## Version
The following are counts of visors listed in the uptime tracker with reward eligible version:
1504 v1.3.28
10 v1.3.29-rc1
## Total number of surveys collected
1755
## Architecture statistics:
1533 arm64
114 amd64
106 arm
## Network Total Memory:
92 Terabytes
## Network Total Ram:
3.0 Terabytes
The minimum version requirement for reward eligibility has been incremented to v1.3.28
The deadline for updating to v1.3.28 is February 1st 2025
Older versions will be ineligible for rewards after this time.
Most visors on the network are already running the requisite version
For rewards on windows, users must run either the latest commits to the develop branch or a release candidate for v1.3.29.
Network Statistics
## Version
The following are counts of visors listed in the uptime tracker with reward eligible version:
1504 v1.3.28
10 v1.3.29-rc1
## Total number of surveys collected
1755
## Architecture statistics:
1533 arm64
114 amd64
106 arm
## Network Total Memory:
92 Terabytes
## Network Total Ram:
3.0 Terabytes
Skywire Routing Errors
The Route Finder is currently experiencing a malfunction after undergoing maintenance last night. We hope to have the service restored ASAP.
Minimum Version Requirement
The minimum version requirement for reward eligibility has been incremented to v1.3.28 effective February 1st 2025.
The Route Finder is currently experiencing a malfunction after undergoing maintenance last night. We hope to have the service restored ASAP.
Minimum Version Requirement
The minimum version requirement for reward eligibility has been incremented to v1.3.28 effective February 1st 2025.
Skywire Deployment Upgrade
Minor network instability is anticipated for approximately the next 3 hours while we upgrade some services on the skywire production deployment. Rewards & uptime should remain unaffected.
Minor network instability is anticipated for approximately the next 3 hours while we upgrade some services on the skywire production deployment. Rewards & uptime should remain unaffected.
Skywire Deployment Issue
An issue with the skywire deployment services was observed last night, and has resulted in the loss of uptime data with which to calculate the next reward distribution. The issue appears ongoing and is affecting routes and the ability to connect to remote proxy & vpn servers.
Rewards will be slightly delayed while we attempt to rectify the situation. Previous reward distribution data will be used to cover the missing distribution.
Our apologies for the inconvenience. We are working to resolve these issues as soon as possible. Please remain patient.
For questions or technical assistance ---> @skywire <---
An issue with the skywire deployment services was observed last night, and has resulted in the loss of uptime data with which to calculate the next reward distribution. The issue appears ongoing and is affecting routes and the ability to connect to remote proxy & vpn servers.
Rewards will be slightly delayed while we attempt to rectify the situation. Previous reward distribution data will be used to cover the missing distribution.
Our apologies for the inconvenience. We are working to resolve these issues as soon as possible. Please remain patient.
For questions or technical assistance ---> @skywire <---
Dmsg Deployment Issue
Transient recurring errors with dmsg clients connecting to the dmsg deployment have been observed over the past 24 hours:
We believe this does not affect visors running dmsghttp-config at this time.
High load related to postgres was observed on the dmsg-discovery server.
Steps taken to mitigate the issue have not yet been successful.
This should not affect uptime or rewards, currently.
We are continuing to investigate and address this issue.
For questions or technical assistance ---> @skywire <---
Transient recurring errors with dmsg clients connecting to the dmsg deployment have been observed over the past 24 hours:
[2025-04-14T11:27:12.812227924-05:00] ERROR [dmsgweb]: Failed to perform request. endpoint="http://dmsgd.skywire.skycoin.com/dmsg-discovery/entry/" error="Post "http://dmsgd.skywire.skycoin.com/dmsg-discovery/entry/": EOF"
[2025-04-14T11:27:12.812277522-05:00] WARN [dmsg_client]: Failed to update discovery entry. error="Post "http://dmsgd.skywire.skycoin.com/dmsg-discovery/entry/": EOF"
We believe this does not affect visors running dmsghttp-config at this time.
High load related to postgres was observed on the dmsg-discovery server.
Steps taken to mitigate the issue have not yet been successful.
This should not affect uptime or rewards, currently.
We are continuing to investigate and address this issue.
For questions or technical assistance ---> @skywire <---
Skywire v1.3.30 Released
This release includes various improvements to the cli interface which have been made over the past several months, improvements to dmsg utilities, and, most significantly, fixes to the faulty logic for automatically establishing transports to public visors - or 'public autoconnect' logic.
Public Autoconnect / Automatic Transport Logic Revisions
The public autoconnect logic is among the most critically important pieces of logic in the entire skywire codebase. It's essential that this logic functions optimally in order for enough transports to exist on the network to make multi-hop routes accessible to all users.
With the old, faulty logic, visors would only attempt to connect to a public visor 3 times. Once those attempts had been exhausted - or - if a transport was established and then lost, no further connection attempts would be made by the visor to that public visor for the duration of it's run. Additionally, the public visor was inundated with many more simultaneous attempts to establish transports than it could handle - because every visor on the network was basically attempting to establish transports to a single public visor at the same time.
The updated logic is as follows:
* random delay of 0-5 minutes before the public autoconnect is engaged.
* visors will now also attempt to create sudph transports to any visor which is directly connected to a public visor.
* The derived list of visors to attempt to autoconnect to is now shuffled or randomized
* Public visors themselves will only attempt to auto-connect to other public visors.
* the online status of any visor is checked before attempting to autoconnect to it.
* no limit or cap on connect / reconnect attempts
As the public visor gets more transports, the likelihood of any given visor attempting to connect to that public visor reduces proportionately, further relieving pressure on public visors.
Embedded Deployment Config
Notably, since the last release, the default deployment configurations are now embedded in the skywire binary.
The
Those files may still be created by the user if desired in order to make visors work with a custom deployment.
The embedded deployment defaults are shown with
DMSG Utilities
New options for the method used by dmsg utilities to connect to the dmsg network have been added - using
The new default connection method uses
Versioning & Alternative Installation Methods
Another significant improvement to the software takes advantage of new features in go1.24
Skywire may now be
This is a major improvement from the previous versioning scheme - which required
These revisions allows anyone to run skywire in a relatively simple way, fully compatible with rewards without explicitly installing it, if you have at least go1.24 installed. See here and here for more information.
This release includes various improvements to the cli interface which have been made over the past several months, improvements to dmsg utilities, and, most significantly, fixes to the faulty logic for automatically establishing transports to public visors - or 'public autoconnect' logic.
Public Autoconnect / Automatic Transport Logic Revisions
The public autoconnect logic is among the most critically important pieces of logic in the entire skywire codebase. It's essential that this logic functions optimally in order for enough transports to exist on the network to make multi-hop routes accessible to all users.
With the old, faulty logic, visors would only attempt to connect to a public visor 3 times. Once those attempts had been exhausted - or - if a transport was established and then lost, no further connection attempts would be made by the visor to that public visor for the duration of it's run. Additionally, the public visor was inundated with many more simultaneous attempts to establish transports than it could handle - because every visor on the network was basically attempting to establish transports to a single public visor at the same time.
The updated logic is as follows:
* random delay of 0-5 minutes before the public autoconnect is engaged.
* visors will now also attempt to create sudph transports to any visor which is directly connected to a public visor.
* The derived list of visors to attempt to autoconnect to is now shuffled or randomized
* Public visors themselves will only attempt to auto-connect to other public visors.
* the online status of any visor is checked before attempting to autoconnect to it.
* no limit or cap on connect / reconnect attempts
As the public visor gets more transports, the likelihood of any given visor attempting to connect to that public visor reduces proportionately, further relieving pressure on public visors.
Embedded Deployment Config
Notably, since the last release, the default deployment configurations are now embedded in the skywire binary.
The
dmsghttp-config.json & services-config.json are no longer included as separate files and have been eexcludeed from the release.Those files may still be created by the user if desired in order to make visors work with a custom deployment.
The embedded deployment defaults are shown with
skywire svc conf and skywire svc conf dmsghttp commands - these templates can be modified to support custom deployment configuration. Files defining the custom deployment configuration may be specified to skywire cli config gen via the -S, --svcconf and -D, --dmsgconf flags, respectively.DMSG Utilities
New options for the method used by dmsg utilities to connect to the dmsg network have been added - using
dmsg direct and dmsg http clients. Both of these methods avoid plain http requests to the dmsg-discovery server. The embedded deployment defaults are now used by the dmsg utilities for establishing a connection to the dmsg network.The new default connection method uses
dmsg http to connect to the dmsg network. The original / previous method may be enabled by providing the -Z flag on starting the given dmsg utility such as skywire dmsg curl or skywire dmsg webVersioning & Alternative Installation Methods
Another significant improvement to the software takes advantage of new features in go1.24
Skywire may now be
go run from outside the source - and the version will be correctly set, automatically:$ go run github.com/skycoin/skywire/cmd/skywire@develop
┌─┐┬┌─┬ ┬┬ ┬┬┬─┐┌─┐
└─┐├┴┐└┬┘││││├┬┘├┤
└─┘┴ ┴ ┴ └┴┘┴┴└─└─┘
v1.3.30
This is a major improvement from the previous versioning scheme - which required
git as well as a local copy of the skywire source code to set the version of the binary via ldflags at compile time.These revisions allows anyone to run skywire in a relatively simple way, fully compatible with rewards without explicitly installing it, if you have at least go1.24 installed. See here and here for more information.
Future Work
Due to delays caused by geopolitical instability, we were not able to get everything on this release that we had wanted to include. The next release will change the connection multiplexing library used by dmsg from yamux to smux - in an attempt to address network stability issues. These libraries are not interoperable, so it will be necessary to transition the dmsg servers in the deployment and the visors on the network to use the new library over the coming months, we hope to begin this process with the next release.
Minimum Version Requirement
The deadline for updating to v1.3.30 is August 1st. Older versions will be ineligible for rewards after this time. The mainnet rules article will be updated to reflect this soon.
We offer our sincere thanks and appreciation for your participation in the skywire network.
For questions or technical assistance ---> @skywire <---
Due to delays caused by geopolitical instability, we were not able to get everything on this release that we had wanted to include. The next release will change the connection multiplexing library used by dmsg from yamux to smux - in an attempt to address network stability issues. These libraries are not interoperable, so it will be necessary to transition the dmsg servers in the deployment and the visors on the network to use the new library over the coming months, we hope to begin this process with the next release.
Minimum Version Requirement
The deadline for updating to v1.3.30 is August 1st. Older versions will be ineligible for rewards after this time. The mainnet rules article will be updated to reflect this soon.
We offer our sincere thanks and appreciation for your participation in the skywire network.
For questions or technical assistance ---> @skywire <---
Update Reminder
The deadline for updating to v1.3.30 is August 1st.
Older versions will be ineligible for rewards after this time.
The mainnet rules article has been updated to reflect this.
For questions or technical assistance ---> @skywire <---
The deadline for updating to v1.3.30 is August 1st.
Older versions will be ineligible for rewards after this time.
The mainnet rules article has been updated to reflect this.
For questions or technical assistance ---> @skywire <---
关于币安近期公告及 Maker MKR 代币更名为 SKY 的官方通知
我们在此澄清，Skycoin 加密货币与 Maker“MKR”/“SKY”代币之间，无论过去还是现在，均不存在任何关系、合作关系、附属关系、关联关系或联系。
Skycoin 与 Maker“MKR”/“SKY”代币或任何相关项目或活动均无任何关联。
任何在币安上提及“SKY”代码或“MKR”/“SKY”代币的声明、营销材料、投资计划或公告均与 Skycoin 完全无关，不应与 Skycoin 混淆。
Maker“MKR”/“SKY”代币与 Skycoin 完全独立，任何与之相反的暗示均应被视为虚假且可能存在欺诈行为。
Skycoin 用户和投资者务必谨慎行事，避免被试图将 Skycoin 与“MKR”/“SKY”代币关联或混淆的无关方误导或欺骗（无论有意或无意）。
币安的公告错误地将 Skycoin 称为代币——Skycoin 拥有自己的区块链。
Skycoin 并非代币。Skycoin 从未在任何第三方区块链上成为代币。
* 币安公告
* Maker DAO 升级门户
Skycoin 提供桌面和移动钱包的钱包软件；Skycoin 不推荐或认可任何用于存储或交易 Skycoin 或基于 Skycoin 平台技术创建的其他“光纤币”的第三方钱包软件。
Skycoin 对因第三方项目引起的任何损失、误解或失实陈述不承担任何责任。
我们在此澄清，Skycoin 加密货币与 Maker“MKR”/“SKY”代币之间，无论过去还是现在，均不存在任何关系、合作关系、附属关系、关联关系或联系。
Skycoin 与 Maker“MKR”/“SKY”代币或任何相关项目或活动均无任何关联。
任何在币安上提及“SKY”代码或“MKR”/“SKY”代币的声明、营销材料、投资计划或公告均与 Skycoin 完全无关，不应与 Skycoin 混淆。
Maker“MKR”/“SKY”代币与 Skycoin 完全独立，任何与之相反的暗示均应被视为虚假且可能存在欺诈行为。
Skycoin 用户和投资者务必谨慎行事，避免被试图将 Skycoin 与“MKR”/“SKY”代币关联或混淆的无关方误导或欺骗（无论有意或无意）。
币安的公告错误地将 Skycoin 称为代币——Skycoin 拥有自己的区块链。
Skycoin 并非代币。Skycoin 从未在任何第三方区块链上成为代币。
* 币安公告
* Maker DAO 升级门户
Skycoin 提供桌面和移动钱包的钱包软件；Skycoin 不推荐或认可任何用于存储或交易 Skycoin 或基于 Skycoin 平台技术创建的其他“光纤币”的第三方钱包软件。
Skycoin 对因第三方项目引起的任何损失、误解或失实陈述不承担任何责任。
Official notice with regard to recent announcements from Binance & the Maker MKR Token rebrand to SKY
We wish to clarify - in reference to recent announcements from Binance and other exchanges - that there is no relationship, partnership, affiliation, association, or connection, in the past or at present between Skycoin cryptocurrency and the Maker "MKR" / "SKY" token.
Skycoin has no involvement whatsoever with the Maker "MKR" / "SKY" token or any related programs or associated activities.
Any statements, marketing materials, investment schemes, or announcements referencing the "SKY" ticker on Binance or the "MKR" / "SKY" token are entirely unrelated to Skycoin and should not be conflated with Skycoin.
The Maker "MKR" / "SKY" token is completely independent from Skycoin, any suggestion to the contrary should be treated as false and potentially fraudulent.
Skycoin Users and investors are urged to exercise caution and avoid being misled or deceived (intentionally or not) by unrelated parties attempting to associate or conflate Skycoin with the "MKR" / "SKY" token.
The announcement by Binance incorrectly refers to Skycoin as a token — Skycoin has its own blockchain.
Skycoin is not a token. Skycoin has never been a token on any third-party blockchain.
* Binance Announcement
* Maker DAO upgrade portal
Skycoin provides wallet software for desktop and mobile wallets ; Skycoin does not recommend or endorse any third-party wallet software for storing or transacting Skycoin or other "fiber coins" created with Skycoin platform technologies.
Skycoin accepts no liability or responsibility for any losses, misunderstandings, or misrepresentations arising from third-party projects.
We wish to clarify - in reference to recent announcements from Binance and other exchanges - that there is no relationship, partnership, affiliation, association, or connection, in the past or at present between Skycoin cryptocurrency and the Maker "MKR" / "SKY" token.
Skycoin has no involvement whatsoever with the Maker "MKR" / "SKY" token or any related programs or associated activities.
Any statements, marketing materials, investment schemes, or announcements referencing the "SKY" ticker on Binance or the "MKR" / "SKY" token are entirely unrelated to Skycoin and should not be conflated with Skycoin.
The Maker "MKR" / "SKY" token is completely independent from Skycoin, any suggestion to the contrary should be treated as false and potentially fraudulent.
Skycoin Users and investors are urged to exercise caution and avoid being misled or deceived (intentionally or not) by unrelated parties attempting to associate or conflate Skycoin with the "MKR" / "SKY" token.
The announcement by Binance incorrectly refers to Skycoin as a token — Skycoin has its own blockchain.
Skycoin is not a token. Skycoin has never been a token on any third-party blockchain.
* Binance Announcement
* Maker DAO upgrade portal
Skycoin provides wallet software for desktop and mobile wallets ; Skycoin does not recommend or endorse any third-party wallet software for storing or transacting Skycoin or other "fiber coins" created with Skycoin platform technologies.
Skycoin accepts no liability or responsibility for any losses, misunderstandings, or misrepresentations arising from third-party projects.
Skywire Deployment Issues
We are working to correct an outage of the skywire production deployment.
Be advised that reward distribution will be delayed until the situation is resolved.
The previous reward distribution will be repeated for the days where uptime is affected by this outage.
We are working to correct an outage of the skywire production deployment.
Be advised that reward distribution will be delayed until the situation is resolved.
The previous reward distribution will be repeated for the days where uptime is affected by this outage.
Skywire PSA
Skywire Deployment Issues We are working to correct an outage of the skywire production deployment. Be advised that reward distribution will be delayed until the situation is resolved. The previous reward distribution will be repeated for the days where…
The deployment issues have been resolved.
Skycoin price in the wallet is not accurate
Be advised - It has come to our attention that the price data being displayed in the Skycoin wallet is not that of Skycoin - but instead reflects the price of the Maker DAO / rebranded SKY token because coinpaprika.com is confusing the two tickers.
Be advised - It has come to our attention that the price data being displayed in the Skycoin wallet is not that of Skycoin - but instead reflects the price of the Maker DAO / rebranded SKY token because coinpaprika.com is confusing the two tickers.
Skycoin Trading Suspension & Market Data Inaccuracy
We hope to clarify a confusing situation occurring on several exchanges following the decision by The Maker (MKR) token to rebrand under the name / ticker
We reiterate: the rebranded maker DAO token has absolutely no connection with Skycoin whatsoever.
Certain crypto data aggregation market research platforms - such as coingecko and coinpaprika - are showing either incomplete or incorrect data for Skycoin.
* CoinPaprika, CoinGecko, and CoinMarketCap are confusing Skycoin & the maker DAO rebranded SKY token - causing incorrect market data to be displayed
* These third party services are to blame for incorrect price data shown in the skycoin wallet.
Unfortunately some exchanges (including LBank) get data from these third party services and are currently displaying Skycoin’s information (supply, official site, whitepaper, etc.) on the trading pages of the newly rebranded Maker token (SKY) - and vice versa.
👉 This creates a major confusion & ambiguity - misleading some users to believe they are trading Skycoin when in fact they are trading the rebranded Maker token.
We urge caution and recommend all community members and users to remain vigilant and share this information with anyone who might be misled.
1. Always verify the wallet address format, contract address (if applicable), and explorer before purchasing any coin or token.
2. Do not confuse Skycoin (SKY) with the rebranded Maker token, also called SKY.
3. When in doubt, refer to Skycoin’s official channels for accurate information - or ask for clarification in either @skycoin or @skywire
📌 Skycoin
Official website: https://www.skycoin.com
Explorer: https://explorer.skycoin.com
We have contacted the affected exchanges & crypto data aggregation market research platforms to request that they correct the errors enumerated above.
For questions or technical assistance ---> @skywire <---
We hope to clarify a confusing situation occurring on several exchanges following the decision by The Maker (MKR) token to rebrand under the name / ticker
SKYWe reiterate: the rebranded maker DAO token has absolutely no connection with Skycoin whatsoever.
Certain crypto data aggregation market research platforms - such as coingecko and coinpaprika - are showing either incomplete or incorrect data for Skycoin.
* CoinPaprika, CoinGecko, and CoinMarketCap are confusing Skycoin & the maker DAO rebranded SKY token - causing incorrect market data to be displayed
* These third party services are to blame for incorrect price data shown in the skycoin wallet.
Unfortunately some exchanges (including LBank) get data from these third party services and are currently displaying Skycoin’s information (supply, official site, whitepaper, etc.) on the trading pages of the newly rebranded Maker token (SKY) - and vice versa.
👉 This creates a major confusion & ambiguity - misleading some users to believe they are trading Skycoin when in fact they are trading the rebranded Maker token.
We urge caution and recommend all community members and users to remain vigilant and share this information with anyone who might be misled.
1. Always verify the wallet address format, contract address (if applicable), and explorer before purchasing any coin or token.
2. Do not confuse Skycoin (SKY) with the rebranded Maker token, also called SKY.
3. When in doubt, refer to Skycoin’s official channels for accurate information - or ask for clarification in either @skycoin or @skywire
📌 Skycoin
Official website: https://www.skycoin.com
Explorer: https://explorer.skycoin.com
We have contacted the affected exchanges & crypto data aggregation market research platforms to request that they correct the errors enumerated above.
For questions or technical assistance ---> @skywire <---
Skywire v1.3.31 Released
On this release:
* improved public autoconnect / auto-transport logic
* added new multiplexing library (https://github.com/xtaci/smux)
* fixed skycoin wallet GUI embedding
* included skycoin explorer as
Minimum Version Requirement
The deadline for updating to v1.3.31 is October 18th (2 weeks from now).
Older versions will be ineligible for rewards after this time.
The mainnet rules article will be updated to reflect this soon.
We offer our sincere thanks and appreciation for your participation in the skywire network.
For questions or technical assistance ---> @skywire <---
On this release:
* improved public autoconnect / auto-transport logic
* added new multiplexing library (https://github.com/xtaci/smux)
* fixed skycoin wallet GUI embedding
* included skycoin explorer as
skywire skycoin explorerMinimum Version Requirement
The deadline for updating to v1.3.31 is October 18th (2 weeks from now).
Older versions will be ineligible for rewards after this time.
The mainnet rules article will be updated to reflect this soon.
We offer our sincere thanks and appreciation for your participation in the skywire network.
For questions or technical assistance ---> @skywire <---
Skywire & Dmsg Deployment Issues
We have identified and are working to correct issues with the dmsg and skywire production deployment.
The reward distribution for uptime on October 12th will be repeated going forward until this issue is resolved.
We have identified and are working to correct issues with the dmsg and skywire production deployment.
The reward distribution for uptime on October 12th will be repeated going forward until this issue is resolved.
Skywire PSA
Skywire v1.3.31 Released On this release: * improved public autoconnect / auto-transport logic * added new multiplexing library (https://github.com/xtaci/smux) * fixed skycoin wallet GUI embedding * included skycoin explorer as skywire skycoin explorer …
Notice: the deadline to update your visors to v1.3.31 is today.
The cache of surveys on the reward system will be cleared soon. Surveys will only be collected from visors meeting the minimum version requirement after that.
Rewards will be distributed in a few hours. There is still time to update, if you have not done so already
Current uptime tracker version statistics:
The cache of surveys on the reward system will be cleared soon. Surveys will only be collected from visors meeting the minimum version requirement after that.
Rewards will be distributed in a few hours. There is still time to update, if you have not done so already
Current uptime tracker version statistics:
960 v1.3.31
282 v1.3.30
251 v1.3.28
181 null
73 v1.3.21
22 v1.3.23
20 v1.3.13
18 v1.3.15
18 v1.3.24
17 v1.3.19
14 v1.3.17
10 v1.3.7
7 v1.0.1
6 v1.3.27
6 v1.3.9
3 v1.3.32-0
2 v1.1.0
2 v1.3.10
2 v1.3.8
1 v1.3.11
1 v1.3.14
1 v1.3.31-rc3
1 v1.3.31-rc4