|
gstefans (OP)
|
 |
May 29, 2019, 09:24:03 PM |
|
There are now a bit too many fora for SMLY - thing get a bit lost  Remember the 45% of the coinbase which goes to the charity? Now we're leaning towards sharing this with other charities in the same "business" -educational tech and applications in low - income regions. The obvious first choice is the African Maths Initiative. This income comes in 10 income streams. So we should focus on one at a time. We could try to give an entire stream to a large non - profit like the Malala Fund or UNICEF. But we can also split one, eg give 1/2 stream to AMI. Consider AMI a done deal. Paperwork is needed and we need a bot to do the work - automate the transfers. But this is easy. We've also talked a lot about UBI - Universal Basic Income. That is a really cool concept. Take a look at the video: https://twitter.com/SmileycoinNews/status/1132127161891074048?s=19We should just do this. Mostly use the transaction fee but make it easier with one income stream? First test should be done in a reasonably controlled setting. A classroom |
|
|
|
|
|
|
|
|
|
|
|
|
|
"Bitcoin: mining our own business since 2009" -- Pieter Wuille
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
gstefans (OP)
|
|
June 07, 2019, 09:50:09 AM |
|
IMPORTANT
The Smileycoin hard fork is coming up in about 20 days. We started this process last year by fixing the code and setting the block where this is to be activated. The last few months have seen a lot of testing but this should all be ready to go.
|
|
|
|
|
|
gstefans (OP)
|
|
June 17, 2019, 04:44:06 PM |
|
IMPORTANT
The Smileycoin hard fork is coming up in about 20 days. We started this process last year by fixing the code and setting the block where this is to be activated. The last few months have seen a lot of testing but this should all be ready to go.
Linux users: Please report any errors right here... Fork in 9.6 days!! |
|
|
|
|
|
gstefans (OP)
|
|
June 17, 2019, 11:00:55 PM |
|
Update: The SmileyCoin will hard fork at block 525000, around June 27.
The Linux code update is available on github.
Please remember to back up your wallet.dat file before installing the new code.
A macOS version has been compiled and is about to be uploaded.
Any volunteers to help with the compilation for Windows?
Coinomi will update their wallet.
The HTML5 wallet should need no updating.
|
|
|
|
|
|
gstefans (OP)
|
|
June 18, 2019, 02:55:51 PM |
|
Update: The SmileyCoin will hard fork at block 525000, around June 27.
The Linux code update is available on github.
Please remember to back up your wallet.dat file before installing the new code.
A macOS version has been compiled and is about to be uploaded.
Any volunteers to help with the compilation for Windows?
Coinomi will update their wallet.
The HTML5 wallet should need no updating.
macOS binary is here: https://github.com/tutor-web/smileyCoin/releases/download/v2.2/Smileycoin-Qt.dmgwe need a volunteer or two to test it out... remember to back up wallet.dat first! |
|
|
|
|
|
|
|
gstefans (OP)
|
|
June 19, 2019, 12:03:36 PM |
|
Status report:
Tradesatoshi is upgrading their wallet
Other exchanges are up to date
Explorers are up to date
So far so good
Expected hard fork time: afternoon, Thursday June 27
|
|
|
|
|
|
gstefans (OP)
|
|
June 29, 2019, 02:31:51 PM |
|
This may be a good time for a pat on the back:
We are past the fork!
Most users upgraded in time.
Only the main chain is active.
We seem to have resolved the swings in difficulty.
The mods seem to do exactly what was intended.
Many thanks to everyone who participated!
|
|
|
|
|
|
|
bragiar
Newbie
 Offline
Activity: 3
Merit: 0
|
|
July 09, 2019, 12:45:06 PM |
|
Where does it say to use BDB 4.8? I think you gave the wrong link. I'm pretty sure the Windows wallet is using BDB 5 |
|
|
|
|
|
|
bragiar
Newbie
Offline
Activity: 3
Merit: 0
|
|
July 10, 2019, 10:42:14 PM |
|
You can just ignore it and use BDB 5. The windows and Mac wallets are using BDB 5, and you should be fine using it. You can always open an old wallet.dat file using a software using new BDB, but not the other way around. But back up the wallet.dat file just in case something goes wrong! |
|
|
|
|
|
dgmon
|
|
July 15, 2019, 11:09:18 AM |
|
This is proving very difficult to compile in this Ubuntu 18 VM :/ make[5]: Entering directory '/home/******/****/smileyCoin/src/qt'
CXX libbitcoinqt_a-bitcoin.o
In file included from bitcoin.cpp:223:0:
bitcoin.moc:13:2: error: #error "This file was generated using the moc from 5.9.5. It"
#error "This file was generated using the moc from 5.9.5. It"
^~~~~
bitcoin.moc:14:2: error: #error "cannot be used with the include files from this version of Qt."
#error "cannot be used with the include files from this version of Qt."
^~~~~
bitcoin.moc:15:2: error: #error "(The moc has changed too much.)"
#error "(The moc has changed too much.)"
^~~~~
bitcoin.moc:19:1: error: ‘QT_WARNING_PUSH’ does not name a type; did you mean ‘QT_NO_WARNINGS’?
QT_WARNING_PUSH
^~~~~~~~~~~~~~~
QT_NO_WARNINGS
bitcoin.moc:30:14: error: ‘qt_meta_stringdata_BitcoinCore_t’ does not name a type
static const qt_meta_stringdata_BitcoinCore_t qt_meta_stringdata_BitcoinCore = {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bitcoin.moc: In static member function ‘static void BitcoinCore::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)’:
bitcoin.moc:96:35: error: ‘IndexOfMethod’ is not a member of ‘QMetaObject’
} else if (_c == QMetaObject::IndexOfMethod) {
^~~~~~~~~~~~~
bitcoin.moc: At global scope:
bitcoin.moc:123:35: error: ‘qt_meta_stringdata_BitcoinCore’ was not declared in this scope
{ &QObject::staticMetaObject, qt_meta_stringdata_BitcoinCore.data,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bitcoin.moc:123:35: note: suggested alternative: ‘qt_meta_data_BitcoinCore’
|
|
|
|
|
bragiar
Newbie
Offline
Activity: 3
Merit: 0
|
|
July 17, 2019, 02:01:24 PM |
|
This is proving very difficult to compile in this Ubuntu 18 VM :/ make[5]: Entering directory '/home/******/****/smileyCoin/src/qt'
CXX libbitcoinqt_a-bitcoin.o
In file included from bitcoin.cpp:223:0:
bitcoin.moc:13:2: error: #error "This file was generated using the moc from 5.9.5. It"
#error "This file was generated using the moc from 5.9.5. It"
^~~~~
bitcoin.moc:14:2: error: #error "cannot be used with the include files from this version of Qt."
#error "cannot be used with the include files from this version of Qt."
^~~~~
bitcoin.moc:15:2: error: #error "(The moc has changed too much.)"
#error "(The moc has changed too much.)"
^~~~~
bitcoin.moc:19:1: error: ‘QT_WARNING_PUSH’ does not name a type; did you mean ‘QT_NO_WARNINGS’?
QT_WARNING_PUSH
^~~~~~~~~~~~~~~
QT_NO_WARNINGS
bitcoin.moc:30:14: error: ‘qt_meta_stringdata_BitcoinCore_t’ does not name a type
static const qt_meta_stringdata_BitcoinCore_t qt_meta_stringdata_BitcoinCore = {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bitcoin.moc: In static member function ‘static void BitcoinCore::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)’:
bitcoin.moc:96:35: error: ‘IndexOfMethod’ is not a member of ‘QMetaObject’
} else if (_c == QMetaObject::IndexOfMethod) {
^~~~~~~~~~~~~
bitcoin.moc: At global scope:
bitcoin.moc:123:35: error: ‘qt_meta_stringdata_BitcoinCore’ was not declared in this scope
{ &QObject::staticMetaObject, qt_meta_stringdata_BitcoinCore.data,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bitcoin.moc:123:35: note: suggested alternative: ‘qt_meta_data_BitcoinCore’
Are you trying to build the frontend? It compiled just fine for me without the frontend on Ubuntu 18. However, the error seems to be some kind of a Qt4/5 conflict |
|
|
|
|
|
|
|
gstefans (OP)
|
|
August 01, 2019, 12:32:58 PM |
|
|
|
|
|
|
|
gstefans (OP)
|
|
August 08, 2019, 09:06:37 AM |
|
A wallet upgrade, to v2.2.4, is now available on github.
We would appreciate hearing if you have any problems with the new version. It contains a bug fix to what could potentially happen when handling very large amounts (over 92 million SMLY) in individual transmissions (single UTXOs).
Of course one can not recommend using such large amounts -- this is uncomfortably close to numerical overflow, the way the coins are coded in crypto wallets. It is much safer to stick to lower amounts. For example, if you look at the SmileyCoin Fund you will see that the initial transmissions to the fund were 75 M SMLY each, but there were a fairly large number of those.
But if you NEED to handle such large amounts, then you absolutely need to upgrade.
|
|
|
|
|
odadef11
Newbie
Offline
Activity: 106
Merit: 0
|
|
August 08, 2019, 06:02:22 PM |
|
on the stock exchange www.southxchange.com not working SMLY wallet  |
|
|
|
|
|
gstefans (OP)
|
|
August 08, 2019, 06:29:33 PM |
|
They are in the process of upgrading their wallet (see above). |
|
|
|
|
|
gstefans (OP)
|
|
August 14, 2019, 03:30:29 PM |
|
southXchange and NovaExchange have upgraded their wallets. Again: one can not recommend messing around with over 90M SMLY in one UTXO -- but if you have to, then you also HAVE TO UPGRADE your wallet! A wallet upgrade, to v2.2.4, is now available on github.
We would appreciate hearing if you have any problems with the new version. It contains a bug fix to what could potentially happen when handling very large amounts (over 92 million SMLY) in individual transmissions (single UTXOs).
Of course one can not recommend using such large amounts -- this is uncomfortably close to numerical overflow, the way the coins are coded in crypto wallets. It is much safer to stick to lower amounts. For example, if you look at the SmileyCoin Fund you will see that the initial transmissions to the fund were 75 M SMLY each, but there were a fairly large number of those.
But if you NEED to handle such large amounts, then you absolutely need to upgrade.
|
|
|
|
|
|
