The latest update to @GuardaWallet for iOS now has Ubiq support!
Thank you Guarda Wallet
https://twitter.com/ubiqsmart/status/1111909226706698240
Topic: [ANN][UBQ] Ubiq - Smart Contracts For An Automated World - page 5. (Read 331628 times)
From Twitter:
The latest update to @GuardaWallet for iOS now has Ubiq support!
Thank you Guarda Wallet
https://twitter.com/ubiqsmart/status/1111909226706698240
The latest update to @GuardaWallet for iOS now has Ubiq support!
Thank you Guarda Wallet
https://twitter.com/ubiqsmart/status/1111909226706698240
But I have a lot of UBQ coins on Cryptopia, about $7300,-
And now??
And now??
None of the coins on that site were moved so you should recover them shortly from my understanding. Never leave coins on an exchange unless activly exchanging them.
But I have a lot of UBQ coins on Cryptopia, about $7300,-
And now??
And now??
From Discord:
Today at 12:34 AM
@everyone
Revised: Gubiq version scheme/roadmap
We have just released the binaries for Gubiq 2.2 on Github with the release notes and blog post also mentioning the Gubiq roadmap to come soon™. This release is based on the Geth 1.7.x branch https://github.com/ubiq/go-ubiq/releases/tag/v2.2.0
Additionally, we have revised the version scheme and roadmap to get us on the Geth 1.8 branch sooner (scroll up for the old plan). We are currently working on Gubiq 2.3.
Gubiq 2.1 = Based on Geth 1.6.final branch
Gubiq 2.2 = Based on Geth 1.7 final branch
Gubiq 2.3 = Based on Geth 1.8 final branch
Gubiq 3.0 = Based on Geth 1.8 final branch + Byzantium hard fork
Gubiq 5.0 = Based on Geth 1.8 final branch + Constantinople hard fork
Ubiq Cosmos hub with ESCH as the base staking token
Something we have started discussing in #ubiq-research is the possibility of having ESCH maintaining the governance aspects but also becoming a staking token as a Cosmos hub.
There's more to research as a group with this and there are some links in that channel. It's a new and interesting technology so hopefully we can explore this out as a community.
From Discord:
weifaYesterday at 3:48 PM
We are very excited to announce that GeoCoin will be participating in the CoinFest Vancouver 2019 conference. Events are scheduled for April 1 - 7th, be sure to check out the facebook event for more details. We hope to see you all there!
weifaYesterday at 3:48 PM
We are very excited to announce that GeoCoin will be participating in the CoinFest Vancouver 2019 conference. Events are scheduled for April 1 - 7th, be sure to check out the facebook event for more details. We hope to see you all there!
From Discord:
Last Tuesday at 10:34 PM
@everyone
Cryptopia update
Cryptopia has tweeted out some updates and has opened trading on all the pairs that they have "quantified as secure". This includes ALL the Ubiq Tokens (APX, CEFS, DOT, GEO, QWARK, RICKS): https://support.cryptopia.co.nz/csm?id=kb_article&sys_id=f679f8e5dbd0b3c084ed147a3a961959
As mentioned, we did not anticipate any issues with Ubiq and Ubiq Token funds on Cryptopia. Their recent announcement confirms NO issues with the Ubiq Tokens.
We do NOT anticipate any issues with Ubiq (UBQ) held on Cryptopia as we continue to monitor the address and the funds have NOT moved. The explanation (and also mentioned to us) is that the Cryptopia team has not yet gotten around to moving those UBQ funds to a new address.
Deposits and withdrawals are not yet open. Check out Cryptopia Twitter for more details: https://twitter.com/Cryptopia_NZ
Last Tuesday at 10:34 PM
@everyone
Cryptopia update
Cryptopia has tweeted out some updates and has opened trading on all the pairs that they have "quantified as secure". This includes ALL the Ubiq Tokens (APX, CEFS, DOT, GEO, QWARK, RICKS): https://support.cryptopia.co.nz/csm?id=kb_article&sys_id=f679f8e5dbd0b3c084ed147a3a961959
As mentioned, we did not anticipate any issues with Ubiq and Ubiq Token funds on Cryptopia. Their recent announcement confirms NO issues with the Ubiq Tokens.
We do NOT anticipate any issues with Ubiq (UBQ) held on Cryptopia as we continue to monitor the address and the funds have NOT moved. The explanation (and also mentioned to us) is that the Cryptopia team has not yet gotten around to moving those UBQ funds to a new address.
Deposits and withdrawals are not yet open. Check out Cryptopia Twitter for more details: https://twitter.com/Cryptopia_NZ
From Discord:
@everyone
Pyrus and latest Trezor v1.8 firmware
The latest Trezor v1.8 firmware requires us to upgrade Pyrus to use a new version of Trezor Connect v7 backend API. Currently sending Transactions doesn't work with v1.8 firmware and Pyrus.
Previous firmware v1.7.3 of Trezor works fine with Pyrus.
The quick workaround is to use mycrypto.com or myetherwallet.com and select the Ubiq network and Ubiq HD path. Both sites are tested and work fine.
We'll test and get a fixed version of Pyrus out ASAP!
Thanks to new Ubiq Discord user @ambidextrous1 for reporting the issue!
@everyone
Pyrus and latest Trezor v1.8 firmware
The latest Trezor v1.8 firmware requires us to upgrade Pyrus to use a new version of Trezor Connect v7 backend API. Currently sending Transactions doesn't work with v1.8 firmware and Pyrus.
Previous firmware v1.7.3 of Trezor works fine with Pyrus.
The quick workaround is to use mycrypto.com or myetherwallet.com and select the Ubiq network and Ubiq HD path. Both sites are tested and work fine.
We'll test and get a fixed version of Pyrus out ASAP!
Thanks to new Ubiq Discord user @ambidextrous1 for reporting the issue!
how did you hack cryptopia? Dotcoin ring a bell ? :\ zzz
From Discord:
@everyone
Pyrus and latest Trezor v1.8 firmware
The latest Trezor v1.8 firmware requires us to upgrade Pyrus to use a new version of Trezor Connect v7 backend API. Currently sending Transactions doesn't work with v1.8 firmware and Pyrus.
Previous firmware v1.7.3 of Trezor works fine with Pyrus.
The quick workaround is to use mycrypto.com or myetherwallet.com and select the Ubiq network and Ubiq HD path. Both sites are tested and work fine.
We'll test and get a fixed version of Pyrus out ASAP!
Thanks to new Ubiq Discord user @ambidextrous1 for reporting the issue!
@everyone
Pyrus and latest Trezor v1.8 firmware
The latest Trezor v1.8 firmware requires us to upgrade Pyrus to use a new version of Trezor Connect v7 backend API. Currently sending Transactions doesn't work with v1.8 firmware and Pyrus.
Previous firmware v1.7.3 of Trezor works fine with Pyrus.
The quick workaround is to use mycrypto.com or myetherwallet.com and select the Ubiq network and Ubiq HD path. Both sites are tested and work fine.
We'll test and get a fixed version of Pyrus out ASAP!
Thanks to new Ubiq Discord user @ambidextrous1 for reporting the issue!
From Discord: matt
PiNode short update about gubiq 2.1 and some other related pi node stuff.
https://blog.ubiqsmart.com/pinodes-gubiq-update-other-news-df7ec6aeee43
PiNode short update about gubiq 2.1 and some other related pi node stuff.
https://blog.ubiqsmart.com/pinodes-gubiq-update-other-news-df7ec6aeee43
From Reddit:
Grab some Ubiq gear!
Just wanted to drop a link to some Ubiq inspired Gear from community artist @TunaChum and the art he has posted in Discord. My side project is a website that promotes transparent #RandomActsOfKindness and one such act is listing these amazing illustrations on different products like T-shirts! If you can spare a few clicks please check out some of our other gear like Geocoin and Bitcoin inspired shirts, we funnel all profits from our store back into transparent acts of kindness. When we sell any of our listed artists we funnel those profits back to them personally! New items added daily so give us a follow on Twitter and support some smiles! @Cryptanthropy
https://www.cryptanthropy.com/gear
Grab some Ubiq gear!
Just wanted to drop a link to some Ubiq inspired Gear from community artist @TunaChum and the art he has posted in Discord. My side project is a website that promotes transparent #RandomActsOfKindness and one such act is listing these amazing illustrations on different products like T-shirts! If you can spare a few clicks please check out some of our other gear like Geocoin and Bitcoin inspired shirts, we funnel all profits from our store back into transparent acts of kindness. When we sell any of our listed artists we funnel those profits back to them personally! New items added daily so give us a follow on Twitter and support some smiles! @Cryptanthropy
https://www.cryptanthropy.com/gear
From Discord:
@everyone
Gubiq version scheme/roadmap
We have just release Gubiq 2.1 but we are already working on the next release as well as the update to Fusion which will have the new Gubiq 2.1 node. I've recently discussed the version scheme and roadmap for the Gubiq core node for the year ahead with @xocel. This will involve 4 more releases and 2 hard forks. Look out for a blog post announcing this as well.
These releases will track the final versions of the upstream Geth branches and will involve a 2-step 2-release process. The first release will be matching the final release of that branch and associated updates. We will then perform some hard fork tests. Once that is concluded we will release a new version with a new major number release signaling a hard fork block.
Here is the Gubiq version scheme and roadmap ahead. Note that Gubiq 2.1 is the current release.
Gubiq 2.1 = Based on Geth 1.6.final branch
Gubiq 2.2 = Based on Geth 1.7 final branch
Gubiq 3.0 = Based on Geth 1.7 final branch + Byzantium hard fork
Gubiq 3.1 = Based on Geth 1.8 final branch
Gubiq 5.0 = Based on Geth 1.8 final branch + Constantinople hard fork
To recap: We plan on having 4 Gubiq releases in the year ahead, 2 of these releases will be hard forks. :smiley:
@everyone
Gubiq version scheme/roadmap
We have just release Gubiq 2.1 but we are already working on the next release as well as the update to Fusion which will have the new Gubiq 2.1 node. I've recently discussed the version scheme and roadmap for the Gubiq core node for the year ahead with @xocel. This will involve 4 more releases and 2 hard forks. Look out for a blog post announcing this as well.
These releases will track the final versions of the upstream Geth branches and will involve a 2-step 2-release process. The first release will be matching the final release of that branch and associated updates. We will then perform some hard fork tests. Once that is concluded we will release a new version with a new major number release signaling a hard fork block.
Here is the Gubiq version scheme and roadmap ahead. Note that Gubiq 2.1 is the current release.
Gubiq 2.1 = Based on Geth 1.6.final branch
Gubiq 2.2 = Based on Geth 1.7 final branch
Gubiq 3.0 = Based on Geth 1.7 final branch + Byzantium hard fork
Gubiq 3.1 = Based on Geth 1.8 final branch
Gubiq 5.0 = Based on Geth 1.8 final branch + Constantinople hard fork
To recap: We plan on having 4 Gubiq releases in the year ahead, 2 of these releases will be hard forks. :smiley:
From Discord:
Announcing Gubiq 2.1 - Our biggest release yet!
The Ubiq developers are proud to present to you after months of development and testing Go-Ubiq 2.1. This is the biggest code update to the Gubiq full node that we have ever released.
Gubiq 2.1 is based on the last release of the upstream Geth 1.6.x branch and includes block downloader/synchronization code refactoring, consensus code refactoring and a slew of other optimizations. This release contains around 500 commits merged from upstream Go-Etheruem.
This is an optional release but highly recommended. The Gubiq 2.1 release does not contain any hard forks but sets the stage for a future update to the upstream Geth 1.7.x branch. We will then schedule a hard fork which will include the Byzantium hard fork changes.
As a recap, the last release of Gubiq contained the UIP 1 hard fork which switched out Ethash to our own independent hashing algorithm Ubqhash. Since this hard fork we have observed what we predicted and we were successful in combatting Ethash rental attacks against various chains. These chain reorganization attacks ranged from small chains to the 2nd largest Ethash chain Ethereum Classic.
Read more in our blog post:
https://blog.ubiqsmart.com/announcing-gubiq-2-1-our-biggest-release-yet-75069acb243e
Announcing Gubiq 2.1 - Our biggest release yet!
The Ubiq developers are proud to present to you after months of development and testing Go-Ubiq 2.1. This is the biggest code update to the Gubiq full node that we have ever released.
Gubiq 2.1 is based on the last release of the upstream Geth 1.6.x branch and includes block downloader/synchronization code refactoring, consensus code refactoring and a slew of other optimizations. This release contains around 500 commits merged from upstream Go-Etheruem.
This is an optional release but highly recommended. The Gubiq 2.1 release does not contain any hard forks but sets the stage for a future update to the upstream Geth 1.7.x branch. We will then schedule a hard fork which will include the Byzantium hard fork changes.
As a recap, the last release of Gubiq contained the UIP 1 hard fork which switched out Ethash to our own independent hashing algorithm Ubqhash. Since this hard fork we have observed what we predicted and we were successful in combatting Ethash rental attacks against various chains. These chain reorganization attacks ranged from small chains to the 2nd largest Ethash chain Ethereum Classic.
Read more in our blog post:
https://blog.ubiqsmart.com/announcing-gubiq-2-1-our-biggest-release-yet-75069acb243e
Congrats! Great to read that Ethashrental attacks are able to be stopped. Lots of development going on!
From Discord:
Latest Quarterly report
The latest quarterly report is out. Thanks to @Kris Lester | Ubiq for compiling it! Have a read and give the article some claps on Medium: https://blog.ubiqsmart.com/ubiq-quarterly-report-february-2019-eb29817771e6
Gubiq - Development update
Things are going really well and carrying on from the previous update we have cleaned up and pushed the code to Github for the next release in the following branch: https://github.com/ubiq/go-ubiq/tree/release/2.1
We're going to continue testing more scenarios and different OS's to see what needs to be fixed before we put out a Final release.
Cryptopia
Cryptopia has tweeted out some updates and plans to re-open in a limited mode on Monday: https://twitter.com/Cryptopia_NZ/status/1100964778116210690
As mentioned, we do not anticipate any issues with Ubiq and Ubiq Token funds.
General thanks
Finally, thank you all for being a great crypto community! You are why Ubiq exists. We appreciate all your supportive tweets, efforts to get involved, random banter, crypto insights, camaraderie and for choosing to have Ubiq in your life. :smiley:
Latest Quarterly report
The latest quarterly report is out. Thanks to @Kris Lester | Ubiq for compiling it! Have a read and give the article some claps on Medium: https://blog.ubiqsmart.com/ubiq-quarterly-report-february-2019-eb29817771e6
Gubiq - Development update
Things are going really well and carrying on from the previous update we have cleaned up and pushed the code to Github for the next release in the following branch: https://github.com/ubiq/go-ubiq/tree/release/2.1
We're going to continue testing more scenarios and different OS's to see what needs to be fixed before we put out a Final release.
Cryptopia
Cryptopia has tweeted out some updates and plans to re-open in a limited mode on Monday: https://twitter.com/Cryptopia_NZ/status/1100964778116210690
As mentioned, we do not anticipate any issues with Ubiq and Ubiq Token funds.
General thanks
Finally, thank you all for being a great crypto community! You are why Ubiq exists. We appreciate all your supportive tweets, efforts to get involved, random banter, crypto insights, camaraderie and for choosing to have Ubiq in your life. :smiley:
From Discord:
Announcing Gubiq 2.1 - Our biggest release yet!
The Ubiq developers are proud to present to you after months of development and testing Go-Ubiq 2.1. This is the biggest code update to the Gubiq full node that we have ever released.
Gubiq 2.1 is based on the last release of the upstream Geth 1.6.x branch and includes block downloader/synchronization code refactoring, consensus code refactoring and a slew of other optimizations. This release contains around 500 commits merged from upstream Go-Etheruem.
This is an optional release but highly recommended. The Gubiq 2.1 release does not contain any hard forks but sets the stage for a future update to the upstream Geth 1.7.x branch. We will then schedule a hard fork which will include the Byzantium hard fork changes.
As a recap, the last release of Gubiq contained the UIP 1 hard fork which switched out Ethash to our own independent hashing algorithm Ubqhash. Since this hard fork we have observed what we predicted and we were successful in combatting Ethash rental attacks against various chains. These chain reorganization attacks ranged from small chains to the 2nd largest Ethash chain Ethereum Classic.
Read more in our blog post:
https://blog.ubiqsmart.com/announcing-gubiq-2-1-our-biggest-release-yet-75069acb243e
Announcing Gubiq 2.1 - Our biggest release yet!
The Ubiq developers are proud to present to you after months of development and testing Go-Ubiq 2.1. This is the biggest code update to the Gubiq full node that we have ever released.
Gubiq 2.1 is based on the last release of the upstream Geth 1.6.x branch and includes block downloader/synchronization code refactoring, consensus code refactoring and a slew of other optimizations. This release contains around 500 commits merged from upstream Go-Etheruem.
This is an optional release but highly recommended. The Gubiq 2.1 release does not contain any hard forks but sets the stage for a future update to the upstream Geth 1.7.x branch. We will then schedule a hard fork which will include the Byzantium hard fork changes.
As a recap, the last release of Gubiq contained the UIP 1 hard fork which switched out Ethash to our own independent hashing algorithm Ubqhash. Since this hard fork we have observed what we predicted and we were successful in combatting Ethash rental attacks against various chains. These chain reorganization attacks ranged from small chains to the 2nd largest Ethash chain Ethereum Classic.
Read more in our blog post:
https://blog.ubiqsmart.com/announcing-gubiq-2-1-our-biggest-release-yet-75069acb243e
From Discord:
Cryptopia update
The Ubiq team (specifically @xocel) had set up real-time alerts to monitor the Cryptopia Ubiq and Ubiq Token funds addresses. We recently saw some funds moving. The good new is that Cryptopia staff confirms they are making these transfers so all Ubiq and Ubiq Tokens should be unaffected by the Cryptopia security breach.
Some chat below with a Cryptopia staff member.
https://cdn.discordapp.com/attachments/359605856980959233/546858129657430058/unknown.png
Cryptopia update
The Ubiq team (specifically @xocel) had set up real-time alerts to monitor the Cryptopia Ubiq and Ubiq Token funds addresses. We recently saw some funds moving. The good new is that Cryptopia staff confirms they are making these transfers so all Ubiq and Ubiq Tokens should be unaffected by the Cryptopia security breach.
Some chat below with a Cryptopia staff member.
https://cdn.discordapp.com/attachments/359605856980959233/546858129657430058/unknown.png
That's very good news! I still had some lying around there. I hope that they will be returend to rightful owners and not be distributed to everyone affected.
Support for the Sphere [SPHR] blockchain upgrade
Avatar
Albert
Yesterday at 15:31
Sphere (SPHR) will be upgrading their proof of stake consensus blockchain to an ERC20 token on the Ubiq network utilizing the independent proof of work algorithm Ubqhash.
Users’ Sphere Bittrex exchange balance totals will reflect the total that they had prior to the swap in a 1:5 manner. i.e. 1 SPHR on Bittrex held during the on-exchange snapshot will get you 5 SPHR tokens on the new chain. The old SPHR tokens will no longer be supported by our development team or traded on Bittrex.
Bittrex will re-enable the Sphere (SPHR) wallet when we and the Sphere team agree that the migration is satisfactory.
Note: Bittrex will be closing our SPHR wallet to deposits and withdrawals on 3/6/2019 until the swap is complete. Bittrex will also stop trading the SPHR token to take accurate snapshots of balances around block 1555551. If any SPHR deposits you had sent to Bittrex are not settled (marked as pending) by 12:00 PM PT, on 3/6/2019 (8:00 PM on 03/6/2019 UTC), you may not be credited with SPHR.
We would like to thank the Sphere team for working closely with us.
https://bittrex.zendesk.com/hc/en-us/articles/360023996572-Support-for-the-Sphere-SPHR-blockchain-upgrade
Avatar
Albert
Yesterday at 15:31
Sphere (SPHR) will be upgrading their proof of stake consensus blockchain to an ERC20 token on the Ubiq network utilizing the independent proof of work algorithm Ubqhash.
Users’ Sphere Bittrex exchange balance totals will reflect the total that they had prior to the swap in a 1:5 manner. i.e. 1 SPHR on Bittrex held during the on-exchange snapshot will get you 5 SPHR tokens on the new chain. The old SPHR tokens will no longer be supported by our development team or traded on Bittrex.
Bittrex will re-enable the Sphere (SPHR) wallet when we and the Sphere team agree that the migration is satisfactory.
Note: Bittrex will be closing our SPHR wallet to deposits and withdrawals on 3/6/2019 until the swap is complete. Bittrex will also stop trading the SPHR token to take accurate snapshots of balances around block 1555551. If any SPHR deposits you had sent to Bittrex are not settled (marked as pending) by 12:00 PM PT, on 3/6/2019 (8:00 PM on 03/6/2019 UTC), you may not be credited with SPHR.
We would like to thank the Sphere team for working closely with us.
https://bittrex.zendesk.com/hc/en-us/articles/360023996572-Support-for-the-Sphere-SPHR-blockchain-upgrade
Lots of commits lately for those keeping tabs on development... EG:
iquidus
[go-ubiq:feature/2.1] 216 new commits
93832b6 VERSION, params: begin 1.6.2 release cycle - karalabe
36a800a common/bitutil, consensus/ethash: reusable bitu... - karalabe
2ec5cf1 Merge pull request #14423 from karalabe/bitutil - karalabe
fd5d51c common/bitutil: added data compression algorithm - zsfelfoldi
cf19586 common/bitutil: fix decompression corner cases;... - karalabe
jyap808
[go-ubiq:release/2.1] 494 new commits
4ece9c6 VERSION, params: start 1.5.10 development cycle - karalabe
72dcd3c core, eth, internal: Added debug_getBadBlocks(... - holiman
[c12f4df](https://github.com/ubiq/go-ubiq/commit/c12f4df910e2da1cc5dd28c5c4bbe2d8721e1057) params: core, core/vm, miner: 64bit gas instruc... - obscuren
[15a609d](https://github.com/ubiq/go-ubiq/commit/15a609d5d6613e37e819975ceba01cb5ba735242) whisper: interface changed to simplify the tran... - gluk256
[a973d1d`](https://github.com/ubiq/go-ubiq/commit/a973d1d5233bbd36cbaed0b7235311d4cd529580) Merge pull request #3674 from obscuren/gaz64 - karalabe
iquidus
[go-ubiq:feature/2.1] 216 new commits
93832b6 VERSION, params: begin 1.6.2 release cycle - karalabe
36a800a common/bitutil, consensus/ethash: reusable bitu... - karalabe
2ec5cf1 Merge pull request #14423 from karalabe/bitutil - karalabe
fd5d51c common/bitutil: added data compression algorithm - zsfelfoldi
cf19586 common/bitutil: fix decompression corner cases;... - karalabe
jyap808
[go-ubiq:release/2.1] 494 new commits
4ece9c6 VERSION, params: start 1.5.10 development cycle - karalabe
72dcd3c core, eth, internal: Added debug_getBadBlocks(... - holiman
[c12f4df](https://github.com/ubiq/go-ubiq/commit/c12f4df910e2da1cc5dd28c5c4bbe2d8721e1057) params: core, core/vm, miner: 64bit gas instruc... - obscuren
[15a609d](https://github.com/ubiq/go-ubiq/commit/15a609d5d6613e37e819975ceba01cb5ba735242) whisper: interface changed to simplify the tran... - gluk256
[a973d1d`](https://github.com/ubiq/go-ubiq/commit/a973d1d5233bbd36cbaed0b7235311d4cd529580) Merge pull request #3674 from obscuren/gaz64 - karalabe
From Discord:
Gubiq - Development update
@xocel and I are making steady progress with updating Gubiq to be in-line with Geth version 1.6.x. The 1.6.x releases didn't have any hard forks but had quite a lot of code changes (mostly optimizations and rearranging code).
The good news is that it will have noticeable disk space savings on initial fast sync.
Chain data on new version up to UIP1 block:
1.7G ./gubiq/chaindata
Current chain data usage:
12G ./gubiq/chaindata
So at least 10 GB in disk space freed up.
The new version is planned to be version 2.1. We hope to have this out soon™ after some extra testing and code clean-ups. After that we will then look at a new release which will bring us in-line with the Byzantium hard fork changes!
Gubiq - Development update
@xocel and I are making steady progress with updating Gubiq to be in-line with Geth version 1.6.x. The 1.6.x releases didn't have any hard forks but had quite a lot of code changes (mostly optimizations and rearranging code).
The good news is that it will have noticeable disk space savings on initial fast sync.
Chain data on new version up to UIP1 block:
1.7G ./gubiq/chaindata
Current chain data usage:
12G ./gubiq/chaindata
So at least 10 GB in disk space freed up.
The new version is planned to be version 2.1. We hope to have this out soon™ after some extra testing and code clean-ups. After that we will then look at a new release which will bring us in-line with the Byzantium hard fork changes!
Jump to: