Can´t sync the wallet because of 0 active connections. What can i do?

Edit:


Sometimes 1 connection for a few seconds.

I think all in all it'll be important to a) keep it all 100% public without registration so everyone can see everything and b) give people who do hold Uno and stick around a way to access trades regardless on the Un-ex thing.

You can find that here.

https://chainz.cryptoid.info/uno/#!network

Let's leave it at 'maybe later'. And if it's coming later after proof of concept on another coin in the wild it should be done by Maxwell. But right now we're still busy with ironing out the last update and i feel the community desires a good coin that's not a constant building site, at least for a while.
In 'under construction' conditions the cap won't grow.

I tell you: there will be no longterm demand from it beyond a pump and dump. It's really not that interesting and even too risky for that possible reward.
There is a whole lot of stuff to get right before we can even talk about another hardfork. Right now it's uncalled for. Maybe later.

I think the cap will grow a whole lot more if we can make the last update 100% and say "we're good for a little while" so the community can recover a little from the last very stressfull fork which in the end of the day caused selling instead of buying because it was delivered badly. I don't think we're interested in more screwjobs right now.

Yeah you will need to install that; You can disable it post install.
IIRC the reason was related to Android wallet integration ... for the moment it is required during install.

Compile without the "USE_UPNP" parameter.

net.cpp:19:32: fatal error: miniupnpc/miniwget.h: No such file or directory
compilation terminated.
make: *** [obj/net.o] Error 

Could someone post a few nodes, I can't sync anymore (going through TOR)
thanks

i said this is a very cool project. whether a one man business Limitless Acuity LLC can pull this off is remain to be seen. i understand you are very impressed by Joe's CV, probably quite rightly so, but there are many-many software developers with 20+ years of experience and only a very few of them can pull off what you are hoping from this project. still this is a cool project 

i hoped this project would work out differently than most crypto do, but it seems this is the same and no real progress here. still this is a very cool project.

I see you labelled the burn address with a comment.

Are you able to label other addresses?

If so, you could label all of the top 4 addresses:

I just noticed you don't display the "CLAMspeech" data that is part of each transaction, and also don't seem to show unconfirmed transactions. Neither is a big deal, but both would be useful additions.

Edit: one other wrinkle maybe worth noting is that the "money supply" is kind of weird for CLAM. Millions of addresses were given 4.6 CLAM each in the initial distribution, and most of them have never transacted since. While those are part of the money supply in some sense it's probably more interesting to only consider coins that have at some point been active.

The "getinfo" RPC call includes these lines:

    "moneysupply" : 15145821.13048927,
    "digsupply" : 317403.40414506,
    "stakesupply" : 371419.72641731,
    "activesupply" : 688823.13056237,

"activesupply" is the sum of "digsupply" (all the 4.6 CLAM initial distribution amounts that have ever moved) and "stakesupply" (all the coins created by staking blocks), and is probably a more interesting statistic to use.

Edit2: and since I'm picking nits, it would be useful if the "Summary ... Block Height   475772" on the front page was a link to the latest block. Currently I have to scroll down to the block list before I see any links at all.

Edit3: I hope all this is seen as useful rather than as bitching... but I'd like to be able to click through a chain of transactions. Currently when viewing a transaction the inputs and outputs link to /address/ pages, but it would be more useful to have them link to the pages for the individual transactions they came from / went to. If that was done, there would be no need to show the full txid in text next to each input, since we could just copy the destination URL if we wanted that information, and the page would then fit on my screen without sideways scrolling (some txids take more horizontal space than others, and the longer ones make the whole page a little wider than my screen).

Edit4: The rich-list lists the official burn address (xCLAMBURNXXXXXXXXXXXXXXXXXXX1HaxZH) as being the 2nd richest address. The client considers coins at that address to be burned, and doesn't include them in the moneysupply. See src/main.cpp:


It would be better not to show that address in the rich-list. They are coins that were left over after the developers did the initial distribution. The address is clearly one that was made up without anyone knowing the private key.

5 UNO bounty to solve this Mac problem. I have 25 UNO sitting on the blockchain that I can not access due to the fork. I am trying to get the Mac 0.10 client to run but I get the same message everytime. I have tried all sort but I think it may be due to the fact that I have Macports installed. If anyone can help me to get the wallet up and running I'll give you 5 UNO out of the 25 UNO. Please.

This is the error message I get:

Process:               Unobtanium-Qt [32238]
Path:                  /Applications/Unobtanium-Qt.app/Contents/MacOS/Unobtanium-Qt
Identifier:            io.unobtanium.Unobtanium-Qt
Version:               
Code Type:             X86-64 (Native)
Parent Process:        [1]
Responsible:           Unobtanium-Qt [32238]
User ID:               501

Date/Time:             2015-05-18 05:51:29.760 +0100
OS Version:            Mac OS X 10.10.3 (14D136)
Report Version:        11
Anonymous UUID:        BA94AC5C-A21D-7A27-8D88-E5FDB68C5FFF


Time Awake Since Boot: 77000 seconds

Crashed Thread:        0

Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: @loader_path/libboost_system-mt.dylib
  Referenced from: /Applications/Unobtanium-Qt.app/Contents/Frameworks/libboost_thread-mt.dylib
  Reason: image not found

Binary Images:
    0x7fff62850000 -     0x7fff62886837  dyld (353.2.1) <65DCCB06-339C-3E25-9702-600A28291D0E> /usr/lib/dyld
    0x7fff8ce31000 -     0x7fff8ce33fff  libsystem_sandbox.dylib (358.20.5) <4CF77128-6BE0-3958-B646-707FA9CE61B2> /usr/lib/system/libsystem_sandbox.dylib
    0x7fff8d262000 -     0x7fff8d269ff7  libcompiler_rt.dylib (35) <BF8FC133-EE10-3DA6-9B90-92039E28678F> /usr/lib/system/libcompiler_rt.dylib
    0x7fff8d277000 -     0x7fff8d294fff  libsystem_kernel.dylib (2782.20.48) <EAFD7BD0-0C30-3E7D-9528-F9916BA0167C> /usr/lib/system/libsystem_kernel.dylib
    0x7fff8db19000 -     0x7fff8db19ff7  liblaunch.dylib (559.20.9) <FA89A113-696E-3271-8FE1-A0D7324E8481> /usr/lib/system/liblaunch.dylib
    0x7fff8db1a000 -     0x7fff8deb2ff7  com.apple.CoreFoundation (6.9 - 1153.18) <5C0892B8-9691-341F-9279-CA3A74D59AA0> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff8df3f000 -     0x7fff8df8eff7  libstdc++.6.dylib (104.1) <803F6AC8-87DC-3E24-9E80-729B551F6FFF> /usr/lib/libstdc++.6.dylib
    0x7fff8ed00000 -     0x7fff8f031fff  com.apple.Foundation (6.9 - 1153.20) <F0FF3A5D-C5B7-34A1-9319-DE1EF928E58E> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff8f4ba000 -     0x7fff8f4e2fff  libxpc.dylib (559.20.9) <D35D0DB2-D7BD-3BE4-8378-062BFE545E1D> /usr/lib/system/libxpc.dylib
    0x7fff8fea4000 -     0x7fff8fed4fff  libsystem_m.dylib (3086.1) <1E12AB45-6D96-36D0-A226-F24D9FB0D9D6> /usr/lib/system/libsystem_m.dylib
    0x7fff90c65000 -     0x7fff90c66ff7  libsystem_blocks.dylib (65) <9615D10A-FCA7-3BE4-AA1A-1B195DACE1A1> /usr/lib/system/libsystem_blocks.dylib
    0x7fff90cb6000 -     0x7fff90cb8fff  libsystem_configuration.dylib (699.1.5) <20F3B077-179D-3CB0-A3C1-C8602D53B4DB> /usr/lib/system/libsystem_configuration.dylib
    0x7fff90e03000 -     0x7fff90e3bfff  libsystem_network.dylib (412.20.3) <589A5F67-BE2A-3245-A181-0ECC9B53EB00> /usr/lib/system/libsystem_network.dylib
    0x7fff91385000 -     0x7fff91386ffb  libremovefile.dylib (35) <3485B5F4-6CE8-3C62-8DFD-8736ED6E8531> /usr/lib/system/libremovefile.dylib
    0x7fff91711000 -     0x7fff9171cfff  libcommonCrypto.dylib (60061) <D381EBC6-69D8-31D3-8084-5A80A32CB748> /usr/lib/system/libcommonCrypto.dylib
    0x7fff91993000 -     0x7fff91995ff7  libsystem_coreservices.dylib (9) <41B7C578-5A53-31C8-A96F-C73E030B0938> /usr/lib/system/libsystem_coreservices.dylib
    0x7fff91a2a000 -     0x7fff91a30fff  libsystem_trace.dylib (72.20.1) <840F5301-B55A-3078-90B9-FEFFD6CD741A> /usr/lib/system/libsystem_trace.dylib
    0x7fff91c18000 -     0x7fff91c1bff7  libdyld.dylib (353.2.1) <9EACCA38-291D-38CC-811F-7E9D1451E2D3> /usr/lib/system/libdyld.dylib
    0x7fff922a9000 -     0x7fff922efff7  libauto.dylib (186) <A260789B-D4D8-316A-9490-254767B8A5F1> /usr/lib/libauto.dylib
    0x7fff923f7000 -     0x7fff923f7ff7  libunc.dylib (29) <5676F7EA-C1DF-329F-B006-D2C3022B7D70> /usr/lib/system/libunc.dylib
    0x7fff948c2000 -     0x7fff948edfff  libc++abi.dylib (125) <88A22A0F-87C6-3002-BFBA-AC0F2808B8B9> /usr/lib/libc++abi.dylib
    0x7fff9497f000 -     0x7fff9497ffff  com.apple.CoreServices (62 - 62) <C69DA8A7-B536-34BF-A93F-1C170E2C6D58> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff94980000 -     0x7fff9499cff7  libsystem_malloc.dylib (53.1.1) <19BCC257-5717-3502-A71F-95D65AFA861B> /usr/lib/system/libsystem_malloc.dylib
    0x7fff94b89000 -     0x7fff94b8fff7  libsystem_networkextension.dylib (167.1.10) <29AB225B-D7FB-30ED-9600-65D44B9A9442> /usr/lib/system/libsystem_networkextension.dylib
    0x7fff94b97000 -     0x7fff94bebfff  libc++.1.dylib (120) <1B9530FD-989B-3174-BB1C-BDC159501710> /usr/lib/libc++.1.dylib
    0x7fff94cce000 -     0x7fff94cd0fff  libquarantine.dylib (76.20.1) <7AF90041-2768-378A-925A-D83161863642> /usr/lib/system/libquarantine.dylib
    0x7fff9519b000 -     0x7fff9519bff7  libkeymgr.dylib (28) <77845842-DE70-3CC5-BD01-C3D14227CED5> /usr/lib/system/libkeymgr.dylib
    0x7fff95a7b000 -     0x7fff95a80fff  libsystem_stats.dylib (163.20.16) <FBC3F80F-A0FB-3BD6-9A7E-800DE45F092E> /usr/lib/system/libsystem_stats.dylib
    0x7fff95abd000 -     0x7fff95ac2ff7  libunwind.dylib (35.3) <BE7E51A0-B6EA-3A54-9CCA-9D88F683A6D6> /usr/lib/system/libunwind.dylib
    0x7fff9608d000 -     0x7fff9609efff  libsystem_coretls.dylib (35.20.2) <6084A531-2523-39F8-B030-811FA1A32FB5> /usr/lib/system/libsystem_coretls.dylib
    0x7fff96108000 -     0x7fff96c89ff7  com.apple.AppKit (6.9 - 1347.57) <B214D528-7D1C-39B2-BE36-821D417A0297> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff96c8a000 -     0x7fff96e8446f  libobjc.A.dylib (647) <759E155D-BC42-3D4E-869B-6F57D477177C> /usr/lib/libobjc.A.dylib
    0x7fff96f97000 -     0x7fff96f9fffb  libcopyfile.dylib (118.1.2) <0C68D3A6-ACDD-3EF3-991A-CC82C32AB836> /usr/lib/system/libcopyfile.dylib
    0x7fff97084000 -     0x7fff97110ff7  libsystem_c.dylib (1044.10.1) <86FBED7A-F2C8-3591-AD6F-486DD57E6B6A> /usr/lib/system/libsystem_c.dylib
    0x7fff971e2000 -     0x7fff971ebff7  libsystem_notify.dylib (133.1.1) <61147800-F320-3DAA-850C-BADF33855F29> /usr/lib/system/libsystem_notify.dylib
    0x7fff971ec000 -     0x7fff971edfff  libDiagnosticMessagesClient.dylib (100) <2EE8E436-5CDC-34C5-9959-5BA218D507FB> /usr/lib/libDiagnosticMessagesClient.dylib
    0x7fff978c9000 -     0x7fff978cdfff  libcache.dylib (69) <45E9A2E7-99C4-36B2-BEE3-0C4E11614AD1> /usr/lib/system/libcache.dylib
    0x7fff9847e000 -     0x7fff9847ffff  libsystem_secinit.dylib (18) <581DAD0F-6B63-3A48-B63B-917AF799ABAA> /usr/lib/system/libsystem_secinit.dylib
    0x7fff987e7000 -     0x7fff9885dfe7  libcorecrypto.dylib (233.1.2) <E1789801-3985-3949-B736-6B3378873301> /usr/lib/system/libcorecrypto.dylib
    0x7fff98a1f000 -     0x7fff98a49ff7  libdispatch.dylib (442.1.4) <502CF32B-669B-3709-8862-08188225E4F0> /usr/lib/system/libdispatch.dylib
    0x7fff98a77000 -     0x7fff98a77fff  com.apple.ApplicationServices (48 - 48) <5BF7910B-C328-3BF8-BA4F-CE52B574CE01> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
    0x7fff99221000 -     0x7fff99237ff7  libsystem_asl.dylib (267) <F153AC5B-0542-356E-88C8-20A62CA704E2> /usr/lib/system/libsystem_asl.dylib
    0x7fff992a0000 -     0x7fff992a9fff  libsystem_pthread.dylib (105.10.1) <3103AA7F-3BAE-3673-9649-47FFD7E15C97> /usr/lib/system/libsystem_pthread.dylib
    0x7fff9c14b000 -     0x7fff9c150ff7  libmacho.dylib (862) <126CA2ED-DE91-308F-8881-B9DAEC3C63B6> /usr/lib/system/libmacho.dylib
    0x7fff9c56f000 -     0x7fff9c577fff  libsystem_platform.dylib (63) <64E34079-D712-3D66-9CE2-418624A5C040> /usr/lib/system/libsystem_platform.dylib
    0x7fff9c5ef000 -     0x7fff9c5f0ff3  libSystem.B.dylib (1213) <CCEC13A5-D0D9-31C5-B0B0-1C564B4A20A6> /usr/lib/libSystem.B.dylib
    0x7fff9c6f2000 -     0x7fff9c71afff  libsystem_info.dylib (459.20.1) <AEB3FE62-4763-3050-8352-D6F9AF961AE6> /usr/lib/system/libsystem_info.dylib
    0x7fff9c72f000 -     0x7fff9c737fff  libsystem_dnssd.dylib (561.1.1) <62B70ECA-E40D-3C63-896E-7F00EC386DDB> /usr/lib/system/libsystem_dnssd.dylib

Model: iMac14,3, BootROM IM143.0118.B09, 4 processors, Intel Core i7, 3.1 GHz, 8 GB, SMC 2.17f7
Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343531533641465238412D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343531533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x111), Broadcom BCM43xx 1.0 (7.15.166.24.3)
Bluetooth: Version 4.3.4f4 15601, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: APPLE SSD SD0128F, 121.33 GB
Serial ATA Device: APPLE HDD HTS541010A9E662, 1 TB
USB Device: Android Phone
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: FaceTime HD Camera (Built-in)
USB Device: MG5200 series
Thunderbolt Bus: iMac, Apple Inc., 23.10

So I guess that answers that question. ConnectInputs() is called both when creating a transaction and when checking the transactions in received blocks, and it rejects transactions which don't have enough fees.

Nope.  Not gonna do it.  Read my last.  If you are not backwards compatible with the wallet universally without a mandatory prompt to upgrade, then this coin long term is a failure.  If I have to watch this forum to make this coin work, then this coin is a long term failure.

Guys it's only like a dollar I'm losing.  The point is much more valuable.  I like this coin and not as Jr.Member as you think.

Watch the debug.log - it probably tells you something like:

2015-05-13 07:00:58 ERROR: AcceptToMemoryPool : not enough fees 22f5cf1835d3f2135d10e460af30eb7ccd6329f0cf9f40a730b0726fe76964e2, 10000 < 20000

or:

2015-04-30 16:19:31 CWallet::CreateTransaction failed: transaction too big (104430 >= 100000)

ERROR: AcceptToMemoryPool : not enough fees 02ce86ccb2dcce0841410b4e243363aa80c7aa5978572f9529074eade0040f75, 0 < 10000

Calculating Fee: 
Vout_Count = 50
  Debug: estimated transaction size: 9042 bytes (fee required at 10000 bytes or more)
tx_size_ok = 1
  Debug: transaction priority: 238.31M (fee required at 57.6M or less)
sugg_fee = 0