◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[bitcreditscc]

Hell of a dump, damn, wish I sold some at 4.5K and put some low ball buy orders back in.

Never mind, i'm holding strong, this coin could turn out to be one of the the better coins of 2015, time will tell. 

It's good for those who can now get a chance to buy in.

I'm not really worried about price, i usually worry about deadlines and code.

I just bought more, I couldn't resist Your right this would be a good entry point for someone.

I'm not worried about the current price either, as I know this is only going one place, and that's UP!!!

all that stands between me and happiness is :-

Code:

c:\bitcredit-smsg\src/qt/messagemodel.cpp:346: undefined reference to `json_spirit::write(
json_spirit::Value_impl<json_spirit::Config_vector<std::string> > const&)'

I wish I could code

I'm sure you will figure it out, step away from the keyboard go and have a coffee, it will come.

Listen to this guy, Dev. Clear the mechanism. Walk outside. Go to store. Go for jog.
Momentarily detach and let your subconscious figure shit out.

I figured it out while i was making dinner... BTC devs are the ones who junked the makefile, they left out the jsonb *.cppn files from the build process. I'll give them a pull request to sort things out. So now i am just touching up the basic Ui then we can have a sample version out in an hour or two.

As you can see there is still some work to be done, but overally we are an inch away from making the 31st deadline.

[leigh2k14]

Hell of a dump, damn, wish I sold some at 4.5K and put some low ball buy orders back in.

Never mind, i'm holding strong, this coin could turn out to be one of the the better coins of 2015, time will tell. 

It's good for those who can now get a chance to buy in.

I'm not really worried about price, i usually worry about deadlines and code.

I just bought more, I couldn't resist Your right this would be a good entry point for someone.

I'm not worried about the current price either, as I know this is only going one place, and that's UP!!!

all that stands between me and happiness is :-

Code:

c:\bitcredit-smsg\src/qt/messagemodel.cpp:346: undefined reference to `json_spirit::write(
json_spirit::Value_impl<json_spirit::Config_vector<std::string> > const&)'

I wish I could code

I'm sure you will figure it out, step away from the keyboard go and have a coffee, it will come.

Listen to this guy, Dev. Clear the mechanism. Walk outside. Go to store. Go for jog.
Momentarily detach and let your subconscious figure shit out.

I figured it out while i was making dinner... BTC devs are the ones who junked the makefile, they left out the jsonb *.cppn files from the build process. I'll give them a pull request to sort things out. So now i am just touching up the basic Ui then we can have a sample version out in an hour or two.

As you can see there is still some work to be done, but overally we are an inch away from making the 31st deadline.

Didn't take you long to figure out, well done dev.

[bitcreditscc]

Current list of known issues :

1) CDB error on wallet shutdown.
2) Some wallets getting stuck @ block 40000
 

[bitcreditscc]

1) BACK UP EVERYTHING!!!!!!!
2) DOWNLOAD Win x64 0.30.16.2-rc (Secure)
3) Run it, play around and let me know what you find

What has been excluded ?

Message formatting will have to be manual until we set a standard that is cross DB compatible. There is someone working hard behind the scenes to update and fix the DB handling for messages.


BTW, this is for people who wish to help test things and figure out the system

[bitcreditscc]

working exclusively on the trust engine and related areas.

[LitcoinCollector]

I can design more stuff. But there needs to be consensus on if this corporate identity (logo, colors, font etc.) will be used.
Can't wait for the BN! Bought some more yesterday!
Let me know guys.
Cheers

[thelonecrouton]

the http://bitexp.net explorer seems to be stuck at block 73746. Could whoever maintains it give it a kick please?

And I'd love to play with the new client but still can't build it on linux:

Code:

qt/messagemodel.cpp: In member function ‘MessageModel::StatusCode MessageModel::sendMessages(const QList<SendMessagesRecipient>&, QString)’:
qt/messagemodel.cpp:631:1: warning: control reaches end of non-void function [-Wreturn-type]
 }
 ^
make[2]: *** [qt/qt_libbitcreditqt_a-messagemodel.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/home/stu/Downloads/bicreditsnew-0.30.15c/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/stu/Downloads/bicreditsnew-0.30.15c/src'
make: *** [all-recursive] Error 1

[thelonecrouton]

Current list of known issues :

1) CDB error on wallet shutdown.
2) Some wallets getting stuck @ block 40000
 

In wallet block explorer can't search by address.

[bitcreditscc]

the http://bitexp.net explorer seems to be stuck at block 73746. Could whoever maintains it give it a kick please?

And I'd love to play with the new client but still can't build it on linux:

Code:

qt/messagemodel.cpp: In member function ‘MessageModel::StatusCode MessageModel::sendMessages(const QList<SendMessagesRecipient>&, QString)’:
qt/messagemodel.cpp:631:1: warning: control reaches end of non-void function [-Wreturn-type]
 }
 ^
make[2]: *** [qt/qt_libbitcreditqt_a-messagemodel.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/home/stu/Downloads/bicreditsnew-0.30.15c/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/stu/Downloads/bicreditsnew-0.30.15c/src'
make: *** [all-recursive] Error 1

This is what i find surprising. Thw windows build is doing just fine from the same source. I'll get right on it.

[bitcreditscc]

Current list of known issues :

1) CDB error on wallet shutdown.
2) Some wallets getting stuck @ block 40000
 

In wallet block explorer can't search by address.

the underlying code is incomplete, there are some DB issues i wanted to understand first, it's meant to be used by BN owners as a backup to double check a clients' trust rating.

[topcat363]

so we can expect the release to be delayed?

[bitcreditscc]

so we can expect the release to be delayed?

I still have time. I'll tell you this evening.

frustrated as hell.

[topcat363]

so we can expect the release to be delayed?

I still have time. I'll tell you this evening.

frustrated as hell.

its cool keep us posted

[bitcreditscc]

so we can expect the release to be delayed?

I still have time. I'll tell you this evening.

frustrated as hell.

its cool keep us posted

almost there, just a few errors left caused by the differences in BTC types vs QT types.

[dbt1033]

so we can expect the release to be delayed?

I still have time. I'll tell you this evening.

frustrated as hell.

its cool keep us posted

almost there, just a few errors left caused by the differences in BTC types vs QT types.

Keep at it.  We appreciate your hard work.  This project will be EPIC.

[bitcreditscc]

As usual... one irritating error left. It's like there's a little demon in QT that loves to taunt me.

I'm going to upload the changes now, then spend some time reading QT reference manual and try to figure it out.

For those who know their QT :-

Code:

qt/messagemodel.cpp: In member function ‘virtual QVariant InvoiceItemTableModel::data(const QModelIndex&, int) const’:
qt/messagemodel.cpp:1176:49: error: conversion from ‘int64_t {aka long int}’ to ‘QVariant’ is ambiguous
                     return rec->quantity * rec->price;
                                                 ^
qt/messagemodel.cpp:1176:42: note: candidates are:
                     return rec->quantity * rec->price;
                                          ^
In file included from /usr/include/qt4/QtCore/qabstractitemmodel.h:45:0,
                 from /usr/include/qt4/QtGui/qabstractitemview.h:46,
                 from /usr/include/qt4/QtGui/qheaderview.h:45,
                 from /usr/include/qt4/QtGui/QHeaderView:1,
                 from qt/guiutil.h:11,
                 from qt/messagemodel.cpp:1:
/usr/include/qt4/QtCore/qvariant.h:429:12: note: QVariant::QVariant(void*) <near match>
     inline QVariant(void *) { Q_ASSERT(false); }
            ^
/usr/include/qt4/QtCore/qvariant.h:429:12: note:   no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘void*’
/usr/include/qt4/QtCore/qvariant.h:219:5: note: QVariant::QVariant(Qt::GlobalColor) <near match>
     QVariant(Qt::GlobalColor color);
     ^
/usr/include/qt4/QtCore/qvariant.h:219:5: note:   no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘Qt::GlobalColor’
/usr/include/qt4/QtCore/qvariant.h:186:36: note: QVariant::QVariant(const char*) <near match>
     QT_ASCII_CAST_WARN_CONSTRUCTOR QVariant(const char *str);
                                    ^
/usr/include/qt4/QtCore/qvariant.h:186:36: note:   no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘const char*’
/usr/include/qt4/QtCore/qvariant.h:184:5: note: QVariant::QVariant(float)
     QVariant(float f) { d.is_null = false; d.type = QMetaType::Float; d.data.f = f; }
     ^
/usr/include/qt4/QtCore/qvariant.h:183:5: note: QVariant::QVariant(double)
     QVariant(double d);
     ^
/usr/include/qt4/QtCore/qvariant.h:182:5: note: QVariant::QVariant(bool)
     QVariant(bool b);
     ^
/usr/include/qt4/QtCore/qvariant.h:181:5: note: QVariant::QVariant(qulonglong)
     QVariant(qulonglong ull);
     ^
/usr/include/qt4/QtCore/qvariant.h:180:5: note: QVariant::QVariant(qlonglong)
     QVariant(qlonglong ll);
     ^
/usr/include/qt4/QtCore/qvariant.h:179:5: note: QVariant::QVariant(uint)
     QVariant(uint ui);
     ^
/usr/include/qt4/QtCore/qvariant.h:178:5: note: QVariant::QVariant(int)
     QVariant(int i);
     ^
/usr/include/qt4/QtCore/qvariant.h:169:5: note: QVariant::QVariant(QVariant::Type) <near match>
     QVariant(Type type);
     ^
/usr/include/qt4/QtCore/qvariant.h:169:5: note:   no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘QVariant::Type’
Makefile:5096: recipe for target 'qt/qt_libbitcreditqt_a-messagemodel.o' failed

[bitcreditscc]

BTW, how do you guys feel about reversible transactions?

mainstream tech leaders like B.G have mentioned that the fact that transactions are not reversible makes it difficult to apply in major finance.

I think that our architecture can allow for a different kind of recourse. But it means i will have to develop an impartial method of dispute resolution. Reliance on third party arbitration would then be limited to cases that cannot be dealt with using software eg a party has a dispute over completion of a bounty or something like that. Likely BN owners would use an in built consensus system that would designate the arbitrator at random.

Anyway, just some things to think about. 

[dbt1033]

BTW, how do you guys feel about reversible transactions?

mainstream tech leaders like B.G have mentioned that the fact that transactions are not reversible makes it difficult to apply in major finance.

I think that our architecture can allow for a different kind of recourse. But it means i will have to develop an impartial method of dispute resolution. Reliance on third party arbitration would then be limited to cases that cannot be dealt with using software eg a party has a dispute over completion of a bounty or something like that. Likely BN owners would use an in built consensus system that would designate the arbitrator at random.

Anyway, just some things to think about. 

YES.  That would be revolutionary.

[darkproton]

BTW, how do you guys feel about reversible transactions?

mainstream tech leaders like B.G have mentioned that the fact that transactions are not reversible makes it difficult to apply in major finance.

I think that our architecture can allow for a different kind of recourse. But it means i will have to develop an impartial method of dispute resolution. Reliance on third party arbitration would then be limited to cases that cannot be dealt with using software eg a party has a dispute over completion of a bounty or something like that. Likely BN owners would use an in built consensus system that would designate the arbitrator at random.

Anyway, just some things to think about. 

This sounds extremely promising. Love the idea. Continually impressive work.

[topcat363]

how many coins are there?