Not sure I understand your question. You are sayign that you used 3d-dna for de novo assembly of a genome. 3D-DNA can produce two types of maps, the "assembly" maps and the "sandboxed" maps. The first one is the default, in which the whole genome is treated without breaking thinks into individual chromosomes, as a single unit with coordinates running from 0 to total assembly length. There will be only one chromosome named "assembly". (I do no know what you are referring to when you are saying 0-0 and 1-1). Indeed, up to very recently Juicebox/Juicebox Assembly Tools could not handle chromosomes longer than int, which would have been a problem for all genome-wide assembly maps (given that, e.g., a typical mammal is 3Gb> int). 3D-DNA/JBAT however do not operate an single-basepair resolution, but rather is always dealing with bins of a particular size. (3D-DNA in particular typically builds maps down to 1kb resolution). For this reason the int issue can be worked around via scaling. 3D-DNA does it automatically, when it will remap the whole genome to fit, rescaling all other relevant calculations so that one gets an stritckly equivalent of what one would expect from a genome when working with bins. When you load the assembly file in JBAT the scaling is recognized, and the labels are corrected in Juicebox to represent the original unscaled genome. You can find some references to this workaround on
dnazoo.org assembly pages.