◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[acarterczyz]

This is the next error I'm getting. Is it named differently?

Code:

ubuntu@ip-172-31-19-32:~/bicreditsnew/src$ cd ~/bicreditsnew/src/bitcreditd /usr/local/bin
-bash: cd: /home/ubuntu/bicreditsnew/src/bitcreditd: No such file or directory

[bitcreditscc]

This is the next error I'm getting. Is it named differently?

Code:

/src$ cd ~/bicreditsnew/src/bitcreditd /usr/local/bin
-bash: cd: /home/ubuntu/bicreditsnew/src/bitcreditd: No such file or directory

1) make sure your prompt looks like this

Code:

ubuntu@ip-172-31-19-32:~/bicreditsnew

then paste this

Code:

chmod +x autogen.sh && cd share/ && chmod +x genbuild.sh && cd .. && cd src/leveldb && chmod +x build_detect_platform && cd ../.. && ./autogen.sh &&  ./configure --disable-tests --enable-upnp-default  && make

[acarterczyz]

This is the next error I'm getting. Is it named differently?

Code:

/src$ cd ~/bicreditsnew/src/bitcreditd /usr/local/bin
-bash: cd: /home/ubuntu/bicreditsnew/src/bitcreditd: No such file or directory

1) make sure your prompt looks like this

Code:

ubuntu@ip-172-31-19-32:~/bicreditsnew

then paste this

Code:

chmod +x autogen.sh && cd share/ && chmod +x genbuild.sh && cd .. && cd src/leveldb && chmod +x build_detect_platform && cd ../.. && ./autogen.sh &&  ./configure --disable-tests --enable-upnp-default  && make

Code:

ubuntu@ip-172-31-19-32:~/bicreditsnew$ chmod +x autogen.sh && cd share/ && chmod +x genbuild.sh && cd .. && cd src/leveldb && chmod +x build_detect_platform && cd ../.. && ./autogen.sh &&  ./configure --disable-tests --enable-upnp-default  && make
aclocal: warning: couldn't open directory 'build-aux/m4': No such file or directory
Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
Makefile.am:3:   The usual way to define 'LIBTOOL' is to add 'LT_INIT'
Makefile.am:3:   to 'configure.ac' and run 'aclocal' and 'autoconf' again.
Makefile.am:3:   If 'LT_INIT' is in 'configure.ac', make sure
Makefile.am:3:   its definition is in aclocal's search path.
Makefile.am:45: warning: source file 'src/secp256k1.c' is in a subdirectory,
Makefile.am:45: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding output
automake: object file(s) will be placed in the top-level directory.  However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
Makefile.am:62: warning: source file 'src/bench_inv.c' is in a subdirectory,
Makefile.am:62: but option 'subdir-objects' is disabled
Makefile.am:56: warning: source file 'src/bench_recover.c' is in a subdirectory,
Makefile.am:56: but option 'subdir-objects' is disabled
Makefile.am:59: warning: source file 'src/bench_sign.c' is in a subdirectory,
Makefile.am:59: but option 'subdir-objects' is disabled
Makefile.am:53: warning: source file 'src/bench_verify.c' is in a subdirectory,
Makefile.am:53: but option 'subdir-objects' is disabled
Makefile.am:70: warning: source file 'src/tests.c' is in a subdirectory,
Makefile.am:70: but option 'subdir-objects' is disabled
autoreconf: automake failed with exit status: 1

[jasemoney]

Fixed the Op and took down ICO stuff, however i do not intend to hide the existence of the coins, hopefully once EmpoEx has setup a wallet and we make the address and transaction public. Maybe bittrex would hold a % as well, i am trying to get a hold of their representative.

sorry whats the plan with the ico, are you going to burn the coins, or have an ico sometime in the future..

[bitcreditscc]

Happy to announce that we have been listed on :-

As agreed in the thread, the ICO coins have been placed in the trust of EmpoEx in a an escrow account, please note that this is Escrow, not the actual ICO.

Much love for the EmpoEx team for reaching out and helping us out. You can always watch the coins movement by importing the address in your client (it supports watch only addresses) or by manually searching using the RPC console in your client.

EmpoEx Escrow Address :- 5qH4yHaaaRuX1qKCZdUHXNJdesssNQcUct

[bitcreditscc]

This is the next error I'm getting. Is it named differently?

Code:

/src$ cd ~/bicreditsnew/src/bitcreditd /usr/local/bin
-bash: cd: /home/ubuntu/bicreditsnew/src/bitcreditd: No such file or directory

1) make sure your prompt looks like this

Code:

ubuntu@ip-172-31-19-32:~/bicreditsnew

then paste this

Code:

chmod +x autogen.sh && cd share/ && chmod +x genbuild.sh && cd .. && cd src/leveldb && chmod +x build_detect_platform && cd ../.. && ./autogen.sh &&  ./configure --disable-tests --enable-upnp-default  && make

Code:

ubuntu@ip-172-31-19-32:~/bicreditsnew$ chmod +x autogen.sh && cd share/ && chmod +x genbuild.sh && cd .. && cd src/leveldb && chmod +x build_detect_platform && cd ../.. && ./autogen.sh &&  ./configure --disable-tests --enable-upnp-default  && make
aclocal: warning: couldn't open directory 'build-aux/m4': No such file or directory
Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
Makefile.am:3:   The usual way to define 'LIBTOOL' is to add 'LT_INIT'
Makefile.am:3:   to 'configure.ac' and run 'aclocal' and 'autoconf' again.
Makefile.am:3:   If 'LT_INIT' is in 'configure.ac', make sure
Makefile.am:3:   its definition is in aclocal's search path.
Makefile.am:45: warning: source file 'src/secp256k1.c' is in a subdirectory,
Makefile.am:45: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding output
automake: object file(s) will be placed in the top-level directory.  However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
Makefile.am:62: warning: source file 'src/bench_inv.c' is in a subdirectory,
Makefile.am:62: but option 'subdir-objects' is disabled
Makefile.am:56: warning: source file 'src/bench_recover.c' is in a subdirectory,
Makefile.am:56: but option 'subdir-objects' is disabled
Makefile.am:59: warning: source file 'src/bench_sign.c' is in a subdirectory,
Makefile.am:59: but option 'subdir-objects' is disabled
Makefile.am:53: warning: source file 'src/bench_verify.c' is in a subdirectory,
Makefile.am:53: but option 'subdir-objects' is disabled
Makefile.am:70: warning: source file 'src/tests.c' is in a subdirectory,
Makefile.am:70: but option 'subdir-objects' is disabled
autoreconf: automake failed with exit status: 1

You dont have all the dependencies installed, follow this guide :-

https://github.com/bitcreditscc/bicreditsnew/blob/master/doc/build-unix.md

[acarterczyz]

Thanks. I'm going to hold off on building the linux wallet for now. I mainly wanted to build it so I could mine on linux.

I'm noticing some issues with the windows wallet.
- I can't find my wallet address anywhere.
- A lot of the buttons are blacked out. Trying to send BCR is difficult, as I need to press buttons to send and it's blacked out. (ex: Click the send button and look at the top right.)
- The Show/Hide button, when pressed, hides the wallet but I can't figure out how to unhide my wallet.
- When is the bank going to be available?
- Block hash rate in the block crawler is always 0.
- Check block 6448 in the block crawler and notice the "Value Out" field states it was 500,000,000 BCR when decrypted. Outputs/Inputs are fail.

This is about all I could find with the wallet, other than the occasional crashes (which I think is a Windows 8.1 issue).

[SockPuppetAccount]

Awesome that EmpoEx agreed to hold onto the ICO coins.  Have you talked to them about possibly hosting the ICO there?  2 options I see are running the ICO the way you had planned, maybe since EmpoEx is involved now anyway see if someone representing the exchange can control the BTC address to escrow those funds as well.  It would probably make distribution of the bitcredits easy too as investors could just make an EmpoEx account and EmpoEx could distribute the shares of the coins right through the exchange.  Or just throw all the coins up in a sell wall on EmpoEx for a week.  Problem there is what price to put them at and what to do with the unsold coins.  I think your method of running the ICO is superior than that option.

See, now I know you aren't a scammer as I am dying to flick a BTC at you for some of the ICO coins and you are wasting all this time worrying about silly details like "development" and "fixing bugs".

[bitcreditscc]

Thanks. I'm going to hold off on building the linux wallet for now. I mainly wanted to build it so I could mine on linux.

I'm noticing some issues with the windows wallet.
- I can't find my wallet address anywhere.
- A lot of the buttons are blacked out. Trying to send BCR is difficult, as I need to press buttons to send and it's blacked out. (ex: Click the send button and look at the top right.)
- The Show/Hide button, when pressed, hides the wallet but I can't figure out how to unhide my wallet.
- When is the bank going to be available?
- Block hash rate in the block crawler is always 0.
- Check block 6448 in the block crawler and notice the "Value Out" field states it was 500,000,000 BCR when decrypted. Outputs/Inputs are fail.

This is about all I could find with the wallet, other than the occasional crashes (which I think is a Windows 8.1 issue).

Yes i noticed this and will put up a lot of those fixes within a day.

The Bank, well, i am wary of setting an exact date so let me make a set of promises

1) in one week or two the beta Statistics Engine will be in the standard wallet
2) in two weeks or three the URI system will be tested by a limited group
3) in a month, i would have a demonstration transactions

These are not concrete dates, I like room to operate freely and explore.

[bitcreditscc]

Awesome that EmpoEx agreed to hold onto the ICO coins.  Have you talked to them about possibly hosting the ICO there?  2 options I see are running the ICO the way you had planned, maybe since EmpoEx is involved now anyway see if someone representing the exchange can control the BTC address to escrow those funds as well.  It would probably make distribution of the bitcredits easy too as investors could just make an EmpoEx account and EmpoEx could distribute the shares of the coins right through the exchange.  Or just throw all the coins up in a sell wall on EmpoEx for a week.  Problem there is what price to put them at and what to do with the unsold coins.  I think your method of running the ICO is superior than that option.

See, now I know you aren't a scammer as I am dying to flick a BTC at you for some of the ICO coins and you are wasting all this time worrying about silly details like "development" and "fixing bugs".

I think ICO discussion should start in a week when i have

1) Fixed the Ui, and 2) You guys have tested the statistics engine and maybe a rudimentary loan request.

Hopefully they'll agree to do the ICO my way, that leaves no coins at all.

A lot of the code is always in flux, but i'd like to prove my willingness and ability to deliver.

Hahaha silly details indeed, i just wish there was more development talent around, some small issues would be taken care of without need to divert from Core development.

[bitcreditscc]

1 hour of crypto-community service to take a break from the more complicated stuff.

https://bitcointalk.org/index.php?topic=907490.msg10111761#msg10111761

[bitcreditscc]

How does

3 months wallet life time
Balance = Global Money supply * 0.001
100 transactions

sound for minimum trust rating?

I feel as though those who participate in the ICO should already have default minimum trust attached to their accounts.

[acarterczyz]

Awesome that EmpoEx agreed to hold onto the ICO coins.  Have you talked to them about possibly hosting the ICO there?  2 options I see are running the ICO the way you had planned, maybe since EmpoEx is involved now anyway see if someone representing the exchange can control the BTC address to escrow those funds as well.  It would probably make distribution of the bitcredits easy too as investors could just make an EmpoEx account and EmpoEx could distribute the shares of the coins right through the exchange.  Or just throw all the coins up in a sell wall on EmpoEx for a week.  Problem there is what price to put them at and what to do with the unsold coins.  I think your method of running the ICO is superior than that option.

See, now I know you aren't a scammer as I am dying to flick a BTC at you for some of the ICO coins and you are wasting all this time worrying about silly details like "development" and "fixing bugs".

I think ICO discussion should start in a week when i have

1) Fixed the Ui, and 2) You guys have tested the statistics engine and maybe a rudimentary loan request.

Hopefully they'll agree to do the ICO my way, that leaves no coins at all.

A lot of the code is always in flux, but i'd like to prove my willingness and ability to deliver.

Hahaha silly details indeed, i just wish there was more development talent around, some small issues would be taken care of without need to divert from Core development.

Sounds great! I can't wait! 

[hack_]

funny how projects like this with an actual plan get less attention than the obvious shit out there.

[NoobKidOnTheBlock]

funny how projects like this with an actual plan get less attention than the obvious shit out there.

The only reason why the shit out there gets so much attention of hype is because majority of the posts are from shill accounts from the people hyping and promoting the coins

[Frigga77]

Am I missing a blockexplorer in the OP? Read it 3 times, but cannot seem to find it...

[The_Prof]

Am I missing a blockexplorer in the OP? Read it 3 times, but cannot seem to find it...

Built into the wallet.

[bitcreditscc]

Looks like an awesome coin!
Which exchange has the most volume to buy?

Bittrex has a lot

[bitcreditscc]

we had a small test of the trust engine today, so expect some new tonight.

[bitcreditscc]

While the difficulty now is generally mineable, we are still missing the 1 minute mark. I do not intend to tamper with that again for a while, but i just thought i'd post an advisory, rather than 6 minutes to confirm, it's taking ~ 10 minutes.